Quote:
Originally Posted by pmDavid
pwnified: When I was looking through the stack trace, it was following all kinds of functions I've never seen, and the only one that I could click on and see where it was in my code, was at the bottom where it called the application main.. lol. I really wasn't sure what to make of it.
|
Yeah when it's a memory problem the stack doesn't help much as it usually fails deep inside system calls.
One thing you could do next time, is to enable zombies to help debug it. Right click your executable in xcode (under Executables in the Overview), select Get Info, select Arguments, and under "Veriables to be set in the environment" create a variable called "NSZombieEnabled" and set the value to YES.
Now when running your app, all deallocations get moved to a zombie pool, and it'll throw an exception if the object is referenced with a readable stack. Dont forget to uncheck the NSZombieEnabled when you're done
