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: accessing debug info from code



Thanks! Exactly what I needed.

On Jun 27, 2008, at 11:13 PM, Rick Altherr wrote:


On Jun 27, 2008, at 7:42 PM, lajos kamocsay wrote:

Hello,


Is there a way to get debug information from code?
I'd like to save the source code name, line being executed and the
call stack at certain points in the application while the program is running.



Thanks, -lajos



_______________________________________________
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


A few ideas:
- Use __FILE__ and __LINE__ macros along with backtrace_symbols() from libSystem. This won't be 100% accurate and won't report objective-c methods.
- Use __FILE__ and __LINE__ macros along with backtrace(). Then run the addresses through atos. atos will read the debugging information from the binary and/or dSYM file. The backtrace is guaranteed to be accurate, but it should be close if you aren't using -fomit-frame-pointer.


--
Rick Altherr
Architecture and Performance Group
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: http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden
References: 
 >accessing debug info from code (From: lajos kamocsay <email@hidden>)
 >Re: accessing debug info from code (From: Rick Altherr <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.