Comments on: Crappy Crash Logs http://www.red-sweater.com/blog/439/crappy-crash-logs Mac & Technology Writings by Daniel Jalkut Wed, 17 Mar 2010 22:33:24 +0000 http://wordpress.org/?v=2.9 hourly 1 By: Peter Adler http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135236 Peter Adler Tue, 18 Dec 2007 09:20:15 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135236 Eric: You're absolutely correct, of course - the crash info doesn't get sent to Apple without the user's OK. Since I always send crash info on to whichever relevant party asks for it, I suppose I assume that everyone else does the same, as a matter of computing hygiene :-/ Eric: You’re absolutely correct, of course – the crash info doesn’t get sent to Apple without the user’s OK. Since I always send crash info on to whichever relevant party asks for it, I suppose I assume that everyone else does the same, as a matter of computing hygiene :-/

]]> By: Krishen http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135109 Krishen Tue, 11 Dec 2007 18:16:18 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135109 That's awesome. Thanks for the heads up on this, I foresee it being very useful. That’s awesome. Thanks for the heads up on this, I foresee it being very useful.

]]> By: Eric Albert http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135081 Eric Albert Mon, 10 Dec 2007 03:53:54 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135081 To be clear, the log isn't sent to Apple by default. No logs come in at all unless the user clicks "Send to Apple". I wonder how many people do that, and how many others just close the window and ignore it. To be clear, the log isn’t sent to Apple by default. No logs come in at all unless the user clicks “Send to Apple”. I wonder how many people do that, and how many others just close the window and ignore it.

]]> By: Daniel Jalkut http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135073 Daniel Jalkut Sun, 09 Dec 2007 15:32:56 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135073 Peter: It's true that Apple doesn't share any of that information with developers, and it's a real sore spot for lots of folks. As far as the difficulty of "hooking in" ourselves, it's not trivial to cover all the bases and do it 100% correctly. So like most things, for most developers it becomes a lower priority than simply hacking away at new features. For an application that has a rampant crashing problem I think some kind of "send the report in automatically" system is a good idea to try to reel in the problem. Peter: It’s true that Apple doesn’t share any of that information with developers, and it’s a real sore spot for lots of folks. As far as the difficulty of “hooking in” ourselves, it’s not trivial to cover all the bases and do it 100% correctly. So like most things, for most developers it becomes a lower priority than simply hacking away at new features.

For an application that has a rampant crashing problem I think some kind of “send the report in automatically” system is a good idea to try to reel in the problem.

]]> By: Peter Adler http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135069 Peter Adler Sun, 09 Dec 2007 09:21:19 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135069 What's always seemed strange to me (as a non-programmer) is that while the crashlog is sent to Apple by default, it *isn't* automatically sent to the third-party developer. For a long time, I simply assumed that the developers were informed by Apple, until Michael Tsai disabused me of that assumption in the course of a late-night troubleshooting email exchange in response to a SpamSieve crash - a crash which he was notified about without my intervention. He informed me that developers had to write their own generate-a-message hooks into Apple's logging system. Yuck. How difficult is it to do? If Apple can generate a message to itself, presumably the engine to do it is available to any programmer, yes? Regardless of whether developers know how to interpret Apple's crashlogs or not, I would think that a developer would want to have whatever information Apple is collecting about his app and its problems... What’s always seemed strange to me (as a non-programmer) is that while the crashlog is sent to Apple by default, it *isn’t* automatically sent to the third-party developer. For a long time, I simply assumed that the developers were informed by Apple, until Michael Tsai disabused me of that assumption in the course of a late-night troubleshooting email exchange in response to a SpamSieve crash – a crash which he was notified about without my intervention. He informed me that developers had to write their own generate-a-message hooks into Apple’s logging system. Yuck. How difficult is it to do? If Apple can generate a message to itself, presumably the engine to do it is available to any programmer, yes?

Regardless of whether developers know how to interpret Apple’s crashlogs or not, I would think that a developer would want to have whatever information Apple is collecting about his app and its problems…

]]> By: Todd Stellanova http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135059 Todd Stellanova Sat, 08 Dec 2007 16:13:15 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135059 This is tremendously useful-- thanks for the detailed explanation of how to use this tool! This is tremendously useful– thanks for the detailed explanation of how to use this tool!

]]> By: Cesar Tardaguila http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135056 Cesar Tardaguila Sat, 08 Dec 2007 07:03:36 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135056 Sure, it is a helpful post. Thanks, Daniel Sure, it is a helpful post. Thanks, Daniel

]]> By: Greg Parker http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135036 Greg Parker Thu, 06 Dec 2007 23:51:05 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135036 Of course, the crash log puts the uuid in <>, and the live preview didn't show that. 0x1000 - 0x1ffe +a.out ??? (???) <55280d01e709b47f244ffb9e56dc360d> /Users/gparker/a.out Of course, the crash log puts the uuid in <>, and the live preview didn’t show that.
0×1000 – 0×1ffe +a.out ??? (???) <55280d01e709b47f244ffb9e56dc360d> /Users/gparker/a.out

]]> By: Greg Parker http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135035 Greg Parker Thu, 06 Dec 2007 23:49:20 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135035 If you're using DWARF, there's an additional bit of information to tell you which version of your app crashed. Check the bottom of the crash log: 0x1000 - 0x1ffe +a.out ??? (???) /Users/gparker/a.out That random number is a UUID generated by the linker. Every time you change your code and recompile, the built binary gets a different number. Use the UUID to make sure you're reading symbols from the same version and architecture that your user was running. This works best if your build generates a fully-symboled binary that you then strip and ship, or if you build to a separate .dSYM file. % otool -lv -arch i386 a.out [...] cmd LC_UUID cmdsize 24 uuid 0x55 0x28 0x0d 0x01 0xe7 0x09 0xb4 0x7f 0x24 0x4f 0xfb 0x9e 0x56 0xdc 0x36 0x0d If you’re using DWARF, there’s an additional bit of information to tell you which version of your app crashed.

Check the bottom of the crash log:
0×1000 – 0×1ffe +a.out ??? (???) /Users/gparker/a.out

That random number is a UUID generated by the linker. Every time you change your code and recompile, the built binary gets a different number. Use the UUID to make sure you’re reading symbols from the same version and architecture that your user was running. This works best if your build generates a fully-symboled binary that you then strip and ship, or if you build to a separate .dSYM file.

% otool -lv -arch i386 a.out
[...]
cmd LC_UUID
cmdsize 24
uuid 0×55 0×28 0×0d 0×01 0xe7 0×09 0xb4 0×7f
0×24 0×4f 0xfb 0×9e 0×56 0xdc 0×36 0×0d

]]> By: Chris Suter http://www.red-sweater.com/blog/439/crappy-crash-logs/comment-page-1#comment-135034 Chris Suter Thu, 06 Dec 2007 22:44:43 +0000 http://www.red-sweater.com/blog/439/crappy-crash-logs#comment-135034 There's no need to have a separate build configuration (which is a pain to keep synchronised anyway). We run a script at the end that copies the application at the end of the build and strips at that point. I suspect that we could improve the process now that you have the option of using dSYM bundles with DWARF. I'd have to check to see if that leaves any unwanted symbols in the main executable. I'd also add that we do all release builds on a build server which has the advantage of isolating potential differences in developer machines and gives us access to the exact build objects and logs for any release. There’s no need to have a separate build configuration (which is a pain to keep synchronised anyway).

We run a script at the end that copies the application at the end of the build and strips at that point.

I suspect that we could improve the process now that you have the option of using dSYM bundles with DWARF. I’d have to check to see if that leaves any unwanted symbols in the main executable.

I’d also add that we do all release builds on a build server which has the advantage of isolating potential differences in developer machines and gives us access to the exact build objects and logs for any release.

]]>