Comments on: Getting a useful stack trace from NSException#callStackReturnAddresses

By: August Atlanta iPhone User Group Meeting Follow-up | Atlanta iPhone & iTouch Developers

Wed, 12 Aug 2009 14:06:29 +0000

[...] I had more information about this stack trace!” – come back here and follow the link to: GTM stacktrace information. Its a guide to using Google Toolbox for Mac. This is the same toolbox that provides a simpler [...]

By: AZ

AZ — Fri, 10 Jul 2009 12:31:05 +0000

Works great. Really.

By: gabe

gabe — Sat, 31 Jan 2009 00:17:13 +0000

Oh right on. Yeah I guess I was referring to how you can’t use NSTask in an iphone project, and the advantage of running with the GTMStackTrace stuff is that you can have it automatically dump the trace instead of having to manually run atos after the fact.

By: cosmix

cosmix — Fri, 30 Jan 2009 21:20:21 +0000

Actually, atos works for the iPhone, at least when you have a debug binary of your app.

For those times when the debugger doesn’t play nice, you can use the cryptic stack trace: take the lower addresses (usually, as in the example above, those that are five or six digits long) that actually correspond to your symbols (as opposed to the system functions that are using much higher addresses), convert to hex and run atos with ‘-arch armv6′ on the debug executable (found in build/Debug-iphoneos).

By: Ben’s Dev Blog » Blog Archive » Stack Traces for iPhone development

Sun, 11 Jan 2009 19:47:58 +0000

[...] Hanford posted a great example of using the Google Toolbox for Mac to print human readable stack [...]

By: Alex

Alex — Tue, 30 Dec 2008 22:11:20 +0000

Hi,

This would be great! How can I get GTM set up in my iPhone app (with as small a footprint as possible please).

Thanks