• 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: Release Build Crash Report function offsets
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Release Build Crash Report function offsets


  • Subject: Re: Release Build Crash Report function offsets
  • From: Lawrence Gold <email@hidden>
  • Date: Wed, 01 Aug 2007 10:16:36 -0600

Wesley Smith wrote:
Is there a way in xcode to figure out which line of code caused a
crash from the offsets CrashReporter gives from release builds?  An
example below:

Thread 0 Crashed:
0   com.cycling74.jit.gl.lua            0x31c26e02 Jitobj_getattribute + 1004
1   com.yourcompany.Lua                 0x31c55dd8 luaD_precall + 1071


Basically, how can I find out where Jitobj_getattribute + 1004 is in my code?

If you have an unstripped build that includes STABS debugging information, you can use atos as described here:


	<http://developer.apple.com/technotes/tn2004/tn2123.html>

If you have a .dSYM file, for now you'll be best off using GDB. For example,

gdb /Users/lawrence/Desktop/test/Alexandria.dSYM/Contents/Resources/DWARF/Alexandria

(If the crash is from an architecture that doesn't match yours, add -arch i386 or -arch ppc.)

Then, in GDB, type

	info line *0x31c26e02

and it should show you the corresponding file name and line number.

_______________________________________________
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: 
 >Release Build Crash Report function offsets (From: "Wesley Smith" <email@hidden>)

  • Prev by Date: Re: Release Build Crash Report function offsets
  • Next by Date: Re: Release Build Crash Report function offsets
  • Previous by thread: Re: Release Build Crash Report function offsets
  • Next by thread: Re: Release Build Crash Report function offsets
  • Index(es):
    • Date
    • Thread