What does "Binary Images" mean in a Crash Log

The Binary Images comprise a map that shows the starting and ending address of every module that was linked to your app at the time of the crash. For example, if your app requires a dynamic library named dylibx, and the object code for that library requires 1 Mbyte of memory, when your app starts up the library code will be "mapped" into the logical memory space of your app (Logical memory addresses aren't physical memory addresses; at runtime your app will be assigned some physical memory and the logical memory gets mapped onto that).

So in the above example, the starting address of dylibx might be 0x30000000 so it's ending address would be 0x300FFFFF. You can use this info to find out which module owns the addresses given in other sections of the report. If you see 0x300ABCD you'll know that address is in dylibx.

Here's a fairly readable article on how to interpret a crash log: [http://www.sealiesoftware.com/blog/archive/2008/09/22/objc explain_So_you_crashed_in_objcmsgSend.html]. As you can see, it's possible to get some clues from a crash log even if you don't know anything about the system or the hardware.

Hope that helps!
\- Ray

Crash Reporting for iPhone OS Applications (TN2151) explains how to back symbols into your crash logs if you have both the binary and the dSYM file for your app. It also includes a link to an update of the ''symbolicatecrash'' utility.

\- Ray