iOS Bad place to die..

[martay]

#0 0x300c8c18 in objc_msgSend ()
#1 0x32b30cb0 in HandleMainThreadReleaseSource ()
#2 0x30269aca in CFRunLoopRunSpecific ()
#3 0x30269366 in CFRunLoopRunInMode ()
#4 0x315506c4 in GSEventRunModal ()
#5 0x30a564e4 in -[UIApplication _run] ()
#6 0x30a5fadc in UIApplicationMain ()

Any ideas? It crashed with a EXC_BAD_ACCESS as the app was coming up. I'm hoping somebody will say there's a known bug in the sdk, but I'm not holding my breath..

 

[jstanier]

Any chance you can try and identify the part of the source code causing the problem and post it? Can't really pinpoint anything from just the error message.

 

[PhoneyDeveloper]

The usual cause of a crash in objc_msgSend () is memory corruption. You might take a look at this http://developer.apple.com/technotes/tn2004/tn2124.html

in particular take a look at NSZombie, which I assume also works with the phone SDK.

 

[cpatch]

Is there a good place to die?!

 

[johnnybluejeans]

Any time I've done something to cause my application to die upon startup (to the point where tracing via the debugger cannot narrow it down), it usually has been something I've done wrong in Interface Builder.