iphone - EXC_BAD_ACCESS on lauching, random bug -


I've completed my first app but I'm getting weird EXC_BAD_ACCESS, which is almost all the time

Here's the trace:

  # 0x02adba93 in objc_msg & end # 1 in 0x07022e00 ?? In 3 0x0003999f in # 2 0x028bcbcd _CFAutoreleasePoolPop # - in PurpleEventCallback # 6 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ # in 0x02961dc4 7 0x028c2737 __CFRunLoopDoSource1 in # 8 0x028bf9c3 __CFRunLoopRun in # 9 0x028bf280 CFRunLoopRunSpecific # 10 in 0x028bf1a1 CFRunLoopRunInMode [NSAutoreleasePool release in #] # 4 0x002e9f84 _UIApplicationHandleEvent # 5 0x0310dafa 11 0x002e2226 - [UIApplication _run] # 12 0x002edb58 UIApplicationMain # 13 0x0000282e The main in the main. M: 14  

The strange thing is that the app starts normally, so I really do not understand what's going on and some help will be great :) < / P>

You have over-released

  • Double-click on your executable
  • An object, so when the autoorigery pool is cleared, it is an invalid operation.

    Select the argument and add NSZombieEnabled with the value Yes

Then run your app again, check a nd console - you should tell it that the object Over-release


Comments

Popular posts from this blog

paypal - How to know the URL referrer in PHP? -

oauth - Facebook OAuth2 Logout does not remove fb_ cookie -

wpf - Line breaks and indenting for the XAML of a saved FlowDocument? -