Kommentare zu: Crash Reporter for iPhone Applications (Part 1)

Von: Rama

Rama — Fri, 06 Feb 2009 22:48:57 +0000

I just published “ratos”, an open source shell that you can start in a terminal and past an entire Xcode stack trace and it will decode it. Speeds up using atos.

Announcement/Doc is here: http://myutil.com/2009/2/6/announcing-ratos-a-shell-to-decode-iphone-stack-traces

And you can go straight to the code here: http://github.com/face/ratos/tree/master

-Rama

Von: Christopher Atlan

Christopher Atlan — Thu, 29 Jan 2009 17:53:11 +0000

Hi Maurj,

I fixed the typos, thx!

Christopher

Von: Maurj

Maurj — Thu, 29 Jan 2009 17:44:16 +0000

Hi Chris,

Thanks for the post! I’ve just spotted there’s an error in the MyUncaughtExceptionHandler code:

for (int i=0; i<[callStackArray cout]; i++) {

…should be “count”, not “cout”. (I’m guessing that you want to use frameCount as the loop’s check too – it’s unused otherwise.)

Ironically, using the code as it is causes an exception in the exception handler, resulting in an infinite loop of exceptions

Von: Christopher Atlan

Christopher Atlan — Sun, 09 Nov 2008 15:37:23 +0000

Hi Glenn,

you don’t use the atos tool on the iphone, you use it on your developer box. After you build the application you see in your build folder a dSYM folder which include the needed information for atos.

I still haven’t automated this…

Christopher

Von: Glenn

Glenn — Sat, 08 Nov 2008 23:37:27 +0000

Hi Chris,
Have you managed to find a better solution (as mentioned in the above comment)? I’m trying to get this to work with my iPhone application, but I’m a little confused as to how you use this atos tool from the phone. Are you calling the system atos application directly from within your app?
I’m anxious to get this working as it would greatly improve our debugging cycle. This blog is definitely a great starting point. Perhaps one more post would be useful which details the entirety of the procedure in one place.
Thanks in advance.

Von: Christopher Atlan

Christopher Atlan — Tue, 28 Oct 2008 12:30:27 +0000

Hi Josh, you are right, it's not possible to use the symbolicatecrash script if you not format your crash report exactly as the apple one. I current use atos, Debugging and Symbolizing Crash Dumps in Xcode, but I'm searching a better solution for this. Christopher

Von: Josh

Josh — Tue, 28 Oct 2008 02:05:23 +0000

Chris…

I wonder if you could give a bit more detail on how to symbolicate the stack trace you are generating. I managed to get a reasonable stack trace by using the backtrace_symbols function you mentioned, however the symbols for my application (the ones i need) are missing. When i attempt to symbolicate the stack trace generated by the function above i get the following error from the symbolicate utility:

joshua$ symbolicatecrash maildump.txt ICONtact.app.dSYM
No crash report version in maildump.txt at /Users/joshua/bin/symbolicatecrash line 719.

Running the symbolicate utility against a full from the iPhone crash dump however works fine.

Von: chris

chris — Sun, 26 Oct 2008 23:34:02 +0000

Christopher,

Very nice post. Thank you for sharing..

Von: Mark

Mark — Sun, 19 Oct 2008 15:15:55 +0000

Christopher, this rocks. I’ll implement it right now. Thanks a lot!

Von: Torsten Curdt

Torsten Curdt — Sun, 19 Oct 2008 07:54:18 +0000

There is another option for the Mac http://vafer.org/projects/feedbackreporter/