Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: finding the source code from a crash log



On 29 Mar 2006, at 22:16, Andrew Taylor wrote:

In Codewarrior finding the source code associated with a line in a crash log is simple, disassemble the file with the offending function and go to the line referenced. I get a mix of the source code and corresponding assembly code with offsets from the beginning of the function so I can see where the problem lies. I don't have to run the program or even have any idea how to reproduce the crash.

How do I do the same thing in Xcode?

There's a command line tool called "atos" that you can use to turn addresses
into symbolic information.


You'll need an unstripped copy of your application, and you just type

  atos -o <executable path>

in Terminal, then enter addresses. The program will print out the name of
the containing function and the offset/line number. You need to use the path
of the executable itself (e.g. Terminal.app/Contents/MacOS/Terminal) rather
than the path of the bundle.


See "man atos" for more information.

Kind regards,

Alastair.

--
http://www.alastairs-place.net


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden
References: 
 >finding the source code from a crash log (From: Andrew Taylor <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.