> Yes, that is my thought too. Now I just have to wait for a crash ;-)
And that's why my app contains this gem:
- (IBAction) crashNow: (id) sender
{ *(char*)0=0; }
--
Scott Ribe
scott_r...@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice
__
On 23/01/2009, at 20.33, Jean-Daniel Dupas wrote:
OK, this does not contains as much info as you want.
depending your need, you may activate core dump generation. So you
will be able to launch gdb on the dump to retreive the info you need.
http://developer.apple.com/technotes/tn2004/tn2124
OK, this does not contains as much info as you want.
depending your need, you may activate core dump generation. So you
will be able to launch gdb on the dump to retreive the info you need.
http://developer.apple.com/technotes/tn2004/tn2124.html#SECCOREDUMPS
Le 23 janv. 09 à 20:18, Jean-Dan
It already does it if debug symbols are available.
For example:
3 libnspr.4.dylib 0x00090636 PR_CreateFileMap + 0
(prmmap.c:52)
4 libnss.3.dylib 0x002b9601
PK11_GetInternalKeySlot + 74 (pk11slot.c:1659)
5 org.shadowlab.MyLibrary 0x00052b5f -
Hi,
Is there any way to make CrashReporter show stack frame content and
line numbers instead of signatures and offsets? Maybe a way to make
gdb automatically attach to crashing processes and do a "t a a bt f"
on them?
Thanks,
jules
___
Cocoa
