• 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
Re: XCode and the unreachable breakpoints
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode and the unreachable breakpoints


  • Subject: Re: XCode and the unreachable breakpoints
  • From: Andreas Grosam <email@hidden>
  • Date: Wed, 28 Sep 2005 12:20:27 +0200


On 28.09.2005, at 03:27, Markian Hlynka wrote:

Jonathan,

this sounds somewhat similar to the situation I described. If continue is greyed out, are you sure that it's actually paused, and not still processing somewhere? Check your processor load, and see if it's cranked. Also, what does the code around the breakpoint do? Does it involve any kind of I/O?

Markian

I also experienced that Xcode 2.1 was occasionally busy for a duration of about 10.. 20 mins while debugging. During this, Xcode didn't respond to user events, and showed the spinning pizza.
This happened when stepping, not due to a breakpoint, though - but might have the same reason.


After closing the disassembler view, this issue disappeared.

Already filed a bug report with detailed logs, profiles and descriptions.


Andreas


On Sep 27, 2005, at 17:54, Jonathan del Strother wrote:

*sigh*   XCode is doing its very best to frustrate me this evening.

I have a breakpoint in some code, and I run my app in the debugger. The app pauses, the debugger announces the breakpoint in the status bar at the bottom, but the relevant code isn't displayed in the debugger. There's no backtrace, no local symbols, and the Pause/Continue buttons are stuck on Pause - Continue is greyed out. The debugger console window has a prompt, but if I type a gdb command in there and hit enter, nothing happens.

I've quit and restarted XCode, looked for any suspiciously hanging processes, moved the breakpoint around, rebuilt the project....I'm still having the same problem.


Does anyone else ever get this? I've had it a few times before, and never figured out exactly what causes it or how to fix it.




Oh well, I'm off to restart and see if that changes anything. Stuff like this makes me pine for VS.NET's debugger...

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


This email sent to email@hidden


---- When arguing with an idiot, be sure they aren't doing the same.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


This email sent to email@hidden


_______________________________________________ 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
References: 
 >XCode and the unreachable breakpoints (From: Jonathan del Strother <email@hidden>)
 >Re: XCode and the unreachable breakpoints (From: Markian Hlynka <email@hidden>)

  • Prev by Date: Re: Custom build locations stored in the user file?
  • Next by Date: Re: Version Linking Issues
  • Previous by thread: Re: XCode and the unreachable breakpoints
  • Next by thread: Re: C with C++ in xcode
  • Index(es):
    • Date
    • Thread