Re: Start traces with CrashReporter
Re: Start traces with CrashReporter
- Subject: Re: Start traces with CrashReporter
- From: Jean-Daniel Dupas <email@hidden>
- Date: Fri, 23 Jan 2009 20:18:12 +0100
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 -[KIService
createCertificate:] + 142 (KIService.m:46)
6 org.shadowlab.MySoftware 0x00002b9d -
[MKIAuthorityDocument editorDidEnd:result:context:] + 193
(MKIAuthorityDocument.m:54)
7 com.apple.AppKit 0x964ea233 -[NSApplication
endSheet:returnCode:] + 288
8 org.shadowlab.MySoftware 0x00007578 -[WBWindowController
close:] + 140 (WBWindowController.m:62)
9 org.shadowlab.MySoftware 0x00004086 -[MKIRequestEditor
ok:] + 660 (MKIRequestEditor.m:206)
Le 23 janv. 09 à 19:45, Jules Colding a écrit :
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-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden