« (Buggy ?) Instruments tries to trick me | Main | EXC_BAD_ACCESS and no stack trace == more quality time lost in Xcode »

Betcha can't debug that

Along the lines of those guitar videos here is an Xcode Project, that crashes in the Xcode debugger but not stand alone. I bet you can't debug that!

The expected output of the debugger is:

Running...
memory_pressure: 0memory_pressure: 02010-07-13 21:51:44.114 MoreTroubleInXcode[13281:a0f] I don't blame you.
Program received signal: "SIGABRT".
sharedlibrary apply-load-rules all
Cannot access memory at address 0x0
Cannot access memory at address 0x0
(gdb)
This is most probably unrelated to the problems of my previous log entry, so don't be misled.

Posted by Nat! on July 13, 2010 8:43 PM |

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Search


About

This page contains a single entry from the blog posted on July 13, 2010 8:43 PM.

The previous post in this blog was (Buggy ?) Instruments tries to trick me.

The next post in this blog is EXC_BAD_ACCESS and no stack trace == more quality time lost in Xcode.

Many more can be found on the main index page or by looking through the archives.

Subscribe to this blog's feed
[What is this?]
Powered by
Movable Type 4.34-en
MoreTroubleInXcode.zip