Debugger displays empty call stack & variables window
Debugger displays empty call stack & variables window
- Subject: Debugger displays empty call stack & variables window
- From: Jens Miltner <email@hidden>
- Date: Mon, 11 Jul 2005 16:13:50 +0200
Hi list,
We've stumbled across a strange problem where the Xcode debugger will
display an empty call stack and variables window (essentially it's
defunct at that point) when hitting the first breakpoint in some
source locations.
We can continue from this point, but we can't inspect anything.
There's no hint in the debugger console about something going wrong.
When we set another breakpoint that is being called early (e.g. in
the app constructor), everything works fine afterwards, but if the
critical breakpoint is the first to be hit, the debugger won't
display anything sensible...
Running gdb from the commandline, we can set the same breakpoint and
everything is fully functional (but of course, it's a little more
tedious to do the debugging from the commandline :( )
This is in Xcode 2.1.
Could it be related to multithreading? We used to be able to debug
multiple threads just fine, so I doubt that's the real cause, but it
only seems to happen for breakpoints in threads other than the main
thread...
Did anybody else stumble across this problem?
I'd be happy to file a bug report, but it's really hard to isolate
the problem, so I wondered if anybody else has seen this and could
share some information...
Thanks,
</jum>
_______________________________________________
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