Re: Xcode doesn't show you why it stopped anymore?
Re: Xcode doesn't show you why it stopped anymore?
- Subject: Re: Xcode doesn't show you why it stopped anymore?
- From: Matt Neuburg <email@hidden>
- Date: Tue, 05 Apr 2011 06:36:22 -0700
On Wed, 30 Mar 2011 03:14:17 -0700, G S <email@hidden> said:
>So my iOS app was just bailing for some reason. When debugging (after some
>user interaction), Xcode would simply stop in the main() function. Nothing
>in the UI said "stopped", nor was there any console message about what
>happened.
>
>Turns out a message was being sent to a deallocated instance, but Xcode
>didn't say this anywhere. It wasn't in the console like these errors used
>to be.
>
>Then I tried just having it stop at a breakpoint. Once again, Xcode did not
>say "stopped at breakpoint" anywhere in the UI (or if it did, it must have
>been extremely obscure).
>
>Anybody know what's going on here? This is basic stuff seriously broken.
Thinks: Ha ha, wait until he tries a breakpoint which has been set to perform its actions and automatically continue. The UI tells you it's stopped at the breakpoint when it *isn't* stopped! That'll get him.
m.
--
matt neuburg, phd = email@hidden, <http://www.apeth.net/matt/>
A fool + a tool + an autorelease pool = cool!
Programming iOS 4!
http://www.apeth.net/matt/default.html#iosbook _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden