• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
need help on understanding the crashreporter traces
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

need help on understanding the crashreporter traces


  • Subject: need help on understanding the crashreporter traces
  • From: Arnab Ganguly <email@hidden>
  • Date: Thu, 26 Feb 2009 12:04:35 +0530

Hi,
Guys sorry if it is a wrong group.

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.

OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_CRASH (SIGSEGV)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  1

Thread 0:
0   libSystem.B.dylib                   0x94fe518e wait4 + 10
1   talkback.dylib                      0x00e11571
spStackTraceCollector::crawl(int, spKeyDataStream*, char*, int, char*,
unsigned long*, unsigned long*) + 593 (StackTraceC.cpp:170)
2   talkback.dylib                      0x00e1197d
spStackTraceCollector::Collect(BlackBox&, spKeyDataStream*,
SPIRAL_TRIGGER_CONTEXT*) + 349 (StackTraceC.cpp:253)
3   talkback.dylib                      0x00e12157
spCollectionManager::Collect(spKeyDataStream*, SPIRAL_TRIGGER_CONTEXT*) +
139 (collmgr.cpp:45)
4   talkback.dylib                      0x00e0a828
spSpiralNubCore::Collect(SPIRAL_TRIGGER_CONTEXT*, unsigned char, char*) +
646 (nubcore.cpp:1059)
5   talkback.dylib                      0x00e0ebad
spSpiralNubCore::HandleProgramException(SPIRAL_TRIGGER_CONTEXT*) + 195
(nubcore.cpp:2362)
6   talkback.dylib                      0x00e04d10 FCProcessSignal(int,
UNIX_EXCEPTION_CONTEXT*) + 132
7   talkback.dylib                      0x00e10d57 SignalHandler_10_2(int,
siginfo*, ucontext*) + 579
8  * libSystem.B.dylib                   0x94fe42bb _sigtramp + 43*
9   ???                                 0xffffffff 0 + 4294967295
10  com.apple.CoreFoundation            0x96ab70ae CFRunLoopRunSpecific +
1790
11  com.apple.CoreFoundation            0x96ab7cd8 CFRunLoopRunInMode + 88
12  com.apple.HIToolbox                 0x905cf2c0 RunCurrentEventLoopInMode
+ 283
13  com.apple.HIToolbox                 0x905cf0d9 ReceiveNextEventCommon +
374
14  com.apple.HIToolbox                 0x905cef4d
BlockUntilNextEventMatchingListInMode + 106
15  com.apple.AppKit                    0x94742d7d _DPSNextEvent + 657
16  com.apple.AppKit                    0x94742630 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
17  com.apple.AppKit                    0x9473b66b -[NSApplication run] +
795
18  com.apple.AppKit                    0x947088a4 NSApplicationMain + 574
19  com.aol.aim.desktop                 0x00002f1d 0x1000 + 7965
20  com.aol.aim.desktop                 0x00002852 0x1000 + 6226
21  com.aol.aim.desktop                 0x00002779 0x1000 + 6009

*Thread 1 Crashed:*
0   libSystem.B.dylib                   0x94f7f3ae __semwait_signal + 10
1   libSystem.B.dylib                   0x94fa9d0d
pthread_cond_wait$UNIX2003 + 73
2   ...ple.CoreServices.CarbonCore      0x92b16ecf TSWaitOnCondition + 126
3   ...ple.CoreServices.CarbonCore      0x92af5da6
TSWaitOnConditionTimedRelative + 202
4   ...ple.CoreServices.CarbonCore      0x92b16b4c MPWaitOnQueue + 208
5   ...thesis.MacinTalkSynthesizer      0x04dbb9dd
MTBEWorker::WorkLoop(MTBEWorker*) + 209
6   ...thesis.MacinTalkSynthesizer      0x04dbbb5d MTBEWorkerStartMPTask +
17
7   ...ple.CoreServices.CarbonCore      0x92b150a3 PrivateMPEntryPoint + 56
8   libSystem.B.dylib                   0x94fa9095 _pthread_start + 321
9   libSystem.B.dylib                   0x94fa8f52 thread_start + 34


Thanks
Arnab
_______________________________________________

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

  • Follow-Ups:
    • Re: need help on understanding the crashreporter traces
      • From: Andrew Farmer <email@hidden>
  • Prev by Date: Re: Observing Managed Object Changes
  • Next by Date: Re: Window Animation with setFrame:display:animate: Flickers [solved]
  • Previous by thread: Re: Observing Managed Object Changes
  • Next by thread: Re: need help on understanding the crashreporter traces
  • Index(es):
    • Date
    • Thread