I was testing out, whether the stack trace generated by Talkback matches with that of Apple crash report.It is always matching with Thread 0 irrespective of any other thread crashed.Not sure whether it is correct ? -A
On Thu, Feb 26, 2009 at 12:23 PM, Andrew Farmer <[email protected]> wrote: > On 25 Feb 09, at 22:34, Arnab Ganguly wrote: > >> I am analysing the Apple crash report.So I launched my application and >> tried >> to forcibly (kill -11 pid) crash the application.The app crashed and even >> the Apple crash report got generated. >> The crash report says Thread 1 crashed, but when I go through the stack >> trace of Thread 0 I see sigtramp is being received by Thread 0.Is this >> correct report? >> >> How is the thread received signal is different from the thread that got >> crashed as per the report ?Any help or suggestion would be of great help. >> >> >> I have given below the crash report.The highlighted line shows that signal >> was received by Thread 0 but the crash was happened on Thread 1.I was >> crashing the application forcibly by sending signal 11 from the command >> prompt multiple times.There I am confused or may be way I am interpreting >> is >> incorrect. >> > <snip> > > 1. _sigtramp ("signal trampoline") is an internal routine within libSystem, > not a signal. It's showing up on the main thread because signal handlers are > always run on the main thread (IIRC). > > 2. You're testing this with an application that implements its own crash > handler (Talkback). You'll get much clearer results if you disable this or > test with another application. > > You'll also get much clearer results if you generate an actual segmentation > violation, rather than sending SIGSEGV. The two are not quite equivalent in > Darwin. > _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
