Re: Can't symbolicate crash reports
Re: Can't symbolicate crash reports
- Subject: Re: Can't symbolicate crash reports
- From: Robert Bielik <email@hidden>
- Date: Thu, 19 Jan 2012 18:39:34 +0100
Jerry Krinock skrev 2012-01-19 02:10:
***************************************
*** STEPS TO SYMBOLIZE A CRASH DUMP ***
***************************************
1) Move/copy both the crashing .app and the relevant.dSYM files into the same directory.
[...]
14) If you calculated a slide, tell gdb to get info for the address minus the slide:
(gdb) info line *(<address> -<slide>)
Example:
(gdb) info line *(0x0002ef5f - 0x1000)
Jesus H Christ. Is it really true that there is no way to open/read the crash dump in a less mind-bogglingly complex way ?
Windows:
1. Make sure symbols/sources are in search path of WinDbg
2. Load crash dump in WinDbg
3. Read the stacktrace (with the source code showing EXACTLY the point of the crash)
Now.. wouldn't that be easier?? Oooh, snap... I'm gonna get it now... ;)
/Rob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden