This sounds like a case where the functions that the debugger is
calling to implement its data formatters are deadlocking against
another thread in your program. Try turning off the data formatters
and see if that works. Also, if you will sample the app you are
debugging (you may need to do "sudo sample") and get the Xcode-gdb log
for the session (you can now turn this on in the Debugging pane of the
Xcode Preferences) and file a bug with these two bits of information,
we can probably figure out what's going on.
Jim
On Oct 31, 2007, at 6:31 PM, Doug Knowles wrote:
Hi,
I'm trying to get an app under development working under Leopard,
and the debugger is proving almost useless. There's plenty of room
to believe that I'm doing something wrong, so I'll post my
observations and see what shakes out:
- Often, when the debugger stops at a breakpoint, the call stack is
displayed, but the variable pane is blank.
- Often, single-stepping sends the app and the debugger into limbo;
I never reach the next line, and about all I can do is terminate the
app and start over.
- Almost always, threads other than the main thread can't be
examined. As soon as I switch to another thread, the debugger
display stops updating, and even the console window is non-responsive.
Maybe these are all related, and/or there's some setup I'm missing.
Any advice welcome.
TIA,
Doug K;
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
Jim Ingham
Apple Developer Tools
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
