• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Xcode doesn't show you why it stopped anymore?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode doesn't show you why it stopped anymore?


  • Subject: Xcode doesn't show you why it stopped anymore?
  • From: G S <email@hidden>
  • Date: Wed, 30 Mar 2011 03:14:17 -0700

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.

Thanks for any insight.
 _______________________________________________
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

  • Prev by Date: Re: debugging an iOS silent app crash on device
  • Next by Date: Xcode 4: Getting Library Search Paths
  • Previous by thread: Re: testing receipt validation procedure fails
  • Next by thread: Xcode 4: Getting Library Search Paths
  • Index(es):
    • Date
    • Thread