• 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: Using atos & reading crash logs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using atos & reading crash logs


  • Subject: Re: Using atos & reading crash logs
  • From: Hugh Sontag <email@hidden>
  • Date: Thu, 12 Feb 2009 15:44:58 -0600

I've noticed the same thing. I used to get crash reports with line numbers when debugging information is included with the application (I used STABS, because DSYM didn't seem to work correctly).

Sometime during the last year, I stopped getting source file names and line numbers, just routine names and an offset.

Hugh Sontag
Qdea

On Feb 12, 2009, at 12:32 AM, Rick Altherr wrote:

If you build your release version with a dSYM, then you can use the list of loaded binaries along with atos and the dSYM to get the line it crashed on. In the crash log, look at the crashed thread and write down the address of the function that crashed. Then, scroll down to the list of binaries. Find the binary that contained the address of the function that crashed. Note the start address of the range for that binary. Put the .dSYM next to the app bundle (or framework, binary, etc) and then run atos on the binary providing the start address as the slide value (you may need to adjust the start address depending on if you use prebinding or not and if the first address is your binary is 0x0 or not). Then feed atos the address that crashed and it will tell you the function, file, and line that corresponds to that address.


Thanks for the information. But, I still can't quite get it to work for me.

Prebinding is turned off.

In the crash log I see:

Thread 0 Crashed:
0   net.company.myapp   	0x00f21153 0x1000 + 15860051

and in the Binary Images in the crash log I see:

0x1000 - 0x330afff +net.company.myapp 15.0.0 (0) (???) <b4812abb6146230a06a8ee92a17ba8c3> /path/to/myapp.app/Contents/MacOS/myapp

The address of the crash is within this range, which is what I would expect.



In the finder I see:

myapp.app/
myapp.app.dSYM



From the terminal, I do:

atos -o /path/to/myapp.app/Contents/MacOS/myapp 0x00f21153

and the result is only:

0x00f21153 (in myapp)

which isn't what I was expecting.



My various build options are as described in:

http://developer.apple.com/tools/xcode/symbolizingcrashdumps.html



Any ideas on what I am doing wrong?


_______________________________________________ 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

_______________________________________________ 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: 
 >Using atos & reading crash logs (From: Eric Gorr <email@hidden>)
 >Re: Using atos & reading crash logs (From: Rick Altherr <email@hidden>)
 >Re: Using atos & reading crash logs (From: Eric Gorr <email@hidden>)

  • Prev by Date: Re: not breaking on breakpoints
  • Next by Date: Re: not breaking on breakpoints
  • Previous by thread: Re: Using atos & reading crash logs
  • Next by thread: Re: Using atos & reading crash logs
  • Index(es):
    • Date
    • Thread