• 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: Reading a crash log
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reading a crash log


  • Subject: Re: Reading a crash log
  • From: Ken Thomases <email@hidden>
  • Date: Sun, 24 Jul 2016 19:48:53 -0500

On Jul 24, 2016, at 6:41 PM, William Squires <email@hidden> wrote:
>
> Which way is the call stack in a crash log? I've got a crash log from com.apple.dock.extra that is:

> Is "0" the top of the call stack (i.e. the most recently called method/function), or the bottom (where the call would eventually unwind, had it not crashed.)

Frame 0 is the top of the call stack.

> Also, does the dump for the non-main threads really help out here (in general), or is this usually a red herring?

There's no general case when it comes to debugging.  You never know what will be relevant to figuring things out.  So, crash logs try to capture as much information as is practical.

Note that there's no reason to expect that crashes are usually in the main thread.  And, yes, knowing what the other threads are doing is often useful.

Regards,
Ken


 _______________________________________________
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: 
 >Reading a crash log (From: William Squires <email@hidden>)

  • Prev by Date: Reading a crash log
  • Next by Date: Re: Best way to bind (potentially arbitrarily) large array of buttons?
  • Previous by thread: Reading a crash log
  • Next by thread: Xcode updates, Apple updates
  • Index(es):
    • Date
    • Thread