• 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: Resolving a crash address to position in code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Resolving a crash address to position in code


  • Subject: Re: Resolving a crash address to position in code
  • From: Wim Lewis <email@hidden>
  • Date: Mon, 18 Apr 2011 13:07:07 -0700

On 18 Apr 2011, at 12:38 PM, Nick Zitzmann wrote:
> Did you save the dSYM from when you built the shipping product? If so, then you can use dwarfdump with the --lookup option to look up that address. Don't forget to include the architecture from the crash log.

atos can also read .dSYMs --- it just displays the file and linenumber rather than all the debug info.

> If not, then I don't think you can look that up.

On occasion I'll load the program into gdb and try to guess from the assembly at the crash location what part of the function it must be in. Error-prone and slow, but possible.


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Resolving a crash address to position in code (From: Peter Hudson <email@hidden>)
 >Re: Resolving a crash address to position in code (From: Nick Zitzmann <email@hidden>)

  • Prev by Date: Re: Resolving a crash address to position in code
  • Next by Date: Re: Resolving a crash address to position in code
  • Previous by thread: Re: Resolving a crash address to position in code
  • Next by thread: Re: Resolving a crash address to position in code
  • Index(es):
    • Date
    • Thread