1

When I get a crash report, it doesn't show me the function that caused the crash as it used to. This is from an OSX desktop app.

2   com.myCompany                   0x000000010018d565 0x100156000 + 226661
3   com.apple.CoreFoundation        0x00007fff88de220c __invoking___ + 140
joels
  • 7,249
  • 11
  • 53
  • 94

1 Answers1

1

You can either fiddle with symbolicatecrash, or use the command-line tool atos (as described here).

I've had much better success with the latter. In both cases you need the original binary that created the crash report and its associated .dSYM file if the symbols aren't included in the binary.

Community
  • 1
  • 1
Ben S
  • 68,394
  • 30
  • 171
  • 212
  • I've been using symbolicatecrash with the dsym and doesn't seem to do anything to the file. ./symbolicatecrash -A -v myApp.crash "MyApp.app.dSYM" Is that the command you use? – joels Jan 12 '12 at 22:13
  • Yeah, symbolicatecrash uses a bunch of poorly documented heuristics in an attempt to find the symbols and gives up fairly easily. I would try following the instructions in this answer: http://stackoverflow.com/a/4954949/68507 – Ben S Jan 12 '12 at 22:15
  • I am going to try it thanks. You have had success using atos with desktop apps? – joels Jan 12 '12 at 22:19
  • I've mostly used it for iOS apps, but I really don't see why it wouldn't work for desktop applications, the tool has been around since 1998. – Ben S Jan 12 '12 at 22:21