New crash log format in 10.3.2
Apple introduced a dialog in Mac OS X 10.3 that offers to mail a crash report to Apple if an application crashes. One of the new features in 10.3.2 is more details in the log!
Here's a sample:
Date/Time: 2003-12-18 13:42:22 -0500 OS Version: 10.3.2 (Build 7D24) Report Version: 2
A new version. This is certainly for consumption by an automated tool.
Command: Camino Path: /Volumes/Nightstalker/Applications/Internet/Camino/Camino.app/Contents/MacOS/Camino Version: 0.7.0 (0.7+) PID: 519 Thread: 0
I think path and version are new.
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0 Crashed: 0 org.mozilla.navigator 0x0062e4ac nsBaseWidget::GetRenderingContext() + 0x28 1 org.mozilla.navigator 0x003cd2bc -[ChildView drawRect:] + 0xac 2 <<00000000>> 0x92dc73e8 0 + 0x92dc73e8 3 <<00000000>> 0x92dc3948 0 + 0x92dc3948 [...] 17 <<00000000>> 0x92ded8d0 0 + 0x92ded8d0 18 <<00000000>> 0x92dfe598 0 + 0x92dfe598 19 <<00000000>> 0x92ddecc0 0 + 0x92ddecc0 20 com.apple.CoreFoundation 0x90191ed0 __CFRunLoopDoObservers + 0x194 21 com.apple.CoreFoundation 0x9019176c __CFRunLoopRun + 0x18c 22 com.apple.CoreFoundation 0x901960bc CFRunLoopRunSpecific + 0x148 23 com.apple.HIToolbox 0x927d632c RunCurrentEventLoopInMode + 0xac
Now it traces the file that the symbol came from. Nice.
Thread 6: 0 libSystem.B.dylib 0x90018ce8 semaphore_timedwait_signal_trap + 0x8 1 libSystem.B.dylib 0x9000e888 _pthread_cond_wait + 0x268 2 libnspr4.dylib 0x00e642ec pt_TimedWait + 0xa8 3 libnspr4.dylib 0x00e64550 PR_WaitCondVar + 0x88 4 org.mozilla.navigator 0x00145f24 nsIOThreadPool::ThreadFunc(void*) + 0x74 5 libnspr4.dylib 0x00e693a4 _pt_root + 0xac 6 libSystem.B.dylib 0x900247e8 _pthread_body + 0x28 Binary Images Description: 0x1000 - 0x857fff org.mozilla.navigator 0.7.0 (0.7+) /Volumes/Nightstalker/Applications/Internet/Camino/Camino.app/Contents/MacOS/Camino 0xe4c000 - 0xe7efff libnspr4.dylib /Volumes/Nightstalker/Applications/Internet/Camino/Camino.app/Contents/MacOS/libnspr4.dylib [...] 0x927d0000 - 0x92b53fff com.apple.HIToolbox 1.3.1 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
And a complete listing of everything loaded. Make sure this doesn't reveal more than you care to reveal...
[edit: When I say "everything loaded", I don't mean everything that's on your computer. I just mean every library that's loaded into that process's address space. The caution you need to take is proportional to your paranoia level. Personally, mine's not that high. --Avi 1/2/04]
Comments
I had the identical problem w/ MW, while I didn't identify if as elegantly as you, uninstalling and reinstalling did the trick.
good post.
Posted by: emark | December 27, 2003 2:17 PM
I sure wish there was a way for developers to specify in the app bundle a different destination address for the stack trace. It doesn't much help me when Apple gets the crash logs for my app (not that my apps /ever/ crash.. ;), and I can't see it doing any good for Apple either. This could be fabulously useful for developers, if only they made this small tweak.
Posted by: Dave Hayden | December 29, 2003 8:54 PM