• 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: Interpreting a Crash Log
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Interpreting a Crash Log


  • Subject: Re: Interpreting a Crash Log
  • From: Wim Lewis <email@hidden>
  • Date: Mon, 13 Sep 2010 17:54:17 -0700

On Sep 13, 2010, at 4:15 PM, email@hidden wrote:
> As I understand the entries below from a crash log my app crashed in objc_msgSend which was called from the method changeAColor:newColor in the class BMatrix, 1499 bytes into the method.
>
> How do I find the offending line in the source from this information?

IIRC, you can use atos(1) for this --- see its man page for details. You'll need to make sure of two things: that you're giving atos the same executable (or DWARF dsym file) that the crash report came from, and that you're adjusting for any load slide. You can use the LC_UUIDs to make sure of the first (see the thread that Jerry Krinock linked to).


_______________________________________________

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: 
 >Interpreting a Crash Log (From: email@hidden)

  • Prev by Date: CALayers - printing and flippedness
  • Next by Date: iOS Popup Menus?
  • Previous by thread: Re: Interpreting a Crash Log
  • Next by thread: Re: Interpreting a Crash Log
  • Index(es):
    • Date
    • Thread