• 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
Re: Getting line numbers in crash logs with dwarf
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting line numbers in crash logs with dwarf


  • Subject: Re: Getting line numbers in crash logs with dwarf
  • From: Jeff Johnson <email@hidden>
  • Date: Sun, 16 Mar 2008 09:18:11 -0500

We discussed this off-list, but I'll post here for the sake of other interested parties. It seems that CrashReporter on Leopard will find MyApp.app.dSYM in the same directory as MyApp.app, but it won't find it anywhere else (e.g., MyApp.app/Contents/MacOS), so shipping the dSYM inside the app bundle won't work. CrashReporter on Tiger won't find the dSYM anywhere. Thus, for your particular purpose it looks like STABS is the only option. Unlike DWARF, STABS puts all of the debugging symbols directly in the app's executable.

-Jeff


On Mar 15, 2008, at 10:42 PM, Rosyna wrote:

I noticed that my debug projects compiled with Stabs debug info correctly show the line number of the function in the backtrace in crash logs when run on other people's computer boxes. Is there anyway to reproduce this with dwarf or do I need to switch back to stabs?

Having the line numbers in crash logs for debug builds has been immensely useful in quickly finding and fixing bugs. Especially since I often send people custom one-off debug builds.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Getting line numbers in crash logs with dwarf (From: Rosyna <email@hidden>)

  • Prev by Date: Re: Objective-C++ 2.0 - C++ valued properties
  • Next by Date: Compilation leads to Undefined symbols of a nested static lib
  • Previous by thread: Getting line numbers in crash logs with dwarf
  • Next by thread: Headers in Framework
  • Index(es):
    • Date
    • Thread