• 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: Jerry Krinock <email@hidden>
  • Date: Mon, 13 Sep 2010 17:13:02 -0700

On 2010 Sep 13, at 16:15, 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?

If you *really want to*, read this:

http://www.cocoabuilder.com/archive/cocoa/276690-debugging-stack-traces.html?q=crash+report+line+number#276690

However unless you've made the mistake of writing a method which is 1000 lines long, you can usually find crashing bugs much faster by turning off Twitter, etc. and doing a "what if" critical reading of the errant method.

_______________________________________________

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: Interpreting a Crash Log
  • Next by Date: CALayers - printing and flippedness
  • Previous by thread: Interpreting a Crash Log
  • Next by thread: Re: Interpreting a Crash Log
  • Index(es):
    • Date
    • Thread