Weird XCode-only debug problem
Weird XCode-only debug problem
- Subject: Weird XCode-only debug problem
- From: Tom Harrington <email@hidden>
- Date: Tue, 18 May 2004 17:33:17 -0600
I'm working on some code I'd like to step through in a debugger.
If I do this in XCode, there's a particular point where stepping over
lines blocks for abnormally long times, and where I get messages in the
debugger console reading "Timed out fetching data. Variable display may
be inaccurate." ("Abnormally long" here builds over about three
lines-- from a few seconds up to several minutes, after which I've
killed the process).
When this happens, "top" indicates that the process being debugged
grabs as much CPU time as possible-- this despite the fact that the
code is not multithreaded, and the line I'm trying to step over is as
follows:
int time = 0;
However if I run GDB from the command line and step through the same
code, I have no problems.
I can avoid the trouble in XCode by arranging not to step over the
specific lines where trouble occurs, i.e. by telling the debugger to
"continue" until just a couple of lines later.
I tried cleaning and reindexing the project, to no avail.
Anyone have any idea what's going on, and what to do about it? The
fact that command-line GDB steps through the code normally leads me to
think it's XCode, but it's weird enough that I really don't know what
to think.
This is with XCode 1.2 on Mac OS X 10.3.3.
--
Tom Harrington
email@hidden
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.