Tracking EXC_BAD_ACCESS on iPad

Posted by Aleks on Stack Overflow See other posts from Stack Overflow or by Aleks
Published on 2010-06-03T08:06:54Z Indexed on 2010/06/03 8:14 UTC
Read the original article Hit count: 281

Filed under:
|
|
|
|

I've been using this code to create my UIWindow

UIMyWindow* win = [[UIMyWindow alloc] 
                   initWithFrame:[[UIScreen mainScreen] applicationFrame]];

UIMyWindow isn't anything special it just has a pointer to a C++ class that does some wrapping of ObjectiveC.

Recently my application start crashing after adding some line of code that doesn't have to do anything with the error. The line of code that I added is just allocating a C++ object but the program execution never reaches this line.

Interesting enough my code works in Release.

My only guess is that I made some memory corruption on a completely different place. My questions are: What type of memory corruption that can be? And is there some good practices to track them down?

© Stack Overflow or respective owner

Related posts about memory

Related posts about ipad