Re: Resolving a crash address to position in code

2011-04-18 Thread Jerry Krinock
On 2011 Apr 18, at 13:36, Peter Hudson wrote: > I've hunted around on the web for material on using dwarfdump - but can't > find anything much. > Any suggestions appreciated ! Here is my "cheat sheet" for symbolizing crash dumps. Fortunately, I don't need to use it often enough to remembe

Re: Resolving a crash address to position in code

2011-04-18 Thread Peter Hudson
Thanks for this Nick - I'll give it a go ! I've hunted around on the web for material on using dwarfdump - but can't find anything much. Any suggestions appreciated ! Peter On 18 Apr 2011, at 21:17, Nick Zitzmann wrote: On Apr 18, 2011, at 2:09 PM, Peter Hudson wrote: What is the dS

Re: Resolving a crash address to position in code

2011-04-18 Thread Nick Zitzmann
On Apr 18, 2011, at 2:09 PM, Peter Hudson wrote: > What is the dSYM - and this output was produced from a debug build. dSYM bundles are created if you (1) turned on debugging symbols, and (2) set the information format to "DWARF with dSYM," both in the project or target build settings. I would

Re: Resolving a crash address to position in code

2011-04-18 Thread Peter Hudson
What is the dSYM - and this output was produced from a debug build. Peter On 18 Apr 2011, at 20:38, Nick Zitzmann wrote: On Apr 18, 2011, at 1:26 PM, Peter Hudson wrote: Hi all, I seem to have acquired a repeatable crash problem - which has only just appeared. The log looks like this :-

Re: Resolving a crash address to position in code

2011-04-18 Thread Wim Lewis
On 18 Apr 2011, at 12:38 PM, Nick Zitzmann wrote: > Did you save the dSYM from when you built the shipping product? If so, then > you can use dwarfdump with the --lookup option to look up that address. Don't > forget to include the architecture from the crash log. atos can also read .dSYMs ---

Re: Resolving a crash address to position in code

2011-04-18 Thread Nick Zitzmann
On Apr 18, 2011, at 1:26 PM, Peter Hudson wrote: > Hi all, > > I seem to have acquired a repeatable crash problem - which has only just > appeared. > The log looks like this :- > > OS Version: 10.4.11 (Build 8S2167) > Report Version: 4 > > > PID: 223 > Thread: 0 > > Exception: EXC_BAD_ACCES