• 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: Crash log - "Backtrace not available"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash log - "Backtrace not available"


  • Subject: Re: Crash log - "Backtrace not available"
  • From: Daniel Jalkut <email@hidden>
  • Date: Sat, 08 Oct 2005 11:08:14 -0400

On Oct 8, 2005, at 10:22 AM, Jonathan del Strother wrote:
I've been sent a crash log which doesn't have a backtrace - it just says "Backtrace not available". Umm...any suggestions on debugging this? What might cause it to not give a backtrace?

I think the backtrace depends on following stack frames. The PowerPC stack pointer is $r1, so if you for instance break during your program's execution and slam a new value into $r1, you'll slam your backtrace as well. I'm not sure what kind of corruption is required to prompt "Backtrace not available," but suffice to say there are plenty of ways to screw your stack frame up.


More information on PowerPC stack is available here:

http://developer.apple.com/documentation/mac/runtimehtml/RTArch-59.html

Daniel


_______________________________________________ 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: 
 >Crash log - "Backtrace not available" (From: Jonathan del Strother <email@hidden>)

  • Prev by Date: Re: GDB: Does "catch vfork" work?
  • Next by Date: Re: GDB: Does "catch vfork" work?
  • Previous by thread: Crash log - "Backtrace not available"
  • Next by thread: Moving from OSX 10.3 (XCode 1.5) to OSX 10.4 (XCode 2.1)
  • Index(es):
    • Date
    • Thread