Re: Using watchpoints... (was Re: Possible GCC Bug?)
Re: Using watchpoints... (was Re: Possible GCC Bug?)
- Subject: Re: Using watchpoints... (was Re: Possible GCC Bug?)
- From: Jim Ingham <email@hidden>
- Date: Wed, 9 Apr 2008 17:00:32 -0700
Make sense. I am not on 3.1 yet, so I *don't* think I have seen that
behavior yet. But the problem I was talking about has nothing to do
with the location issue. Rather it has to do with the fact that
Xcode sends gbd an expression that makes gdb barf and the watchpoint
is not set at all, which is why you often have to take a trip to the
debugger console....
I see. There's one bug we fixed recently that would cause the
expression the UI makes up to be incorrect. In that case, you had to
have a pointer to an object whose static type was different from its
dynamic type, and the sub-element you were pointing to had to belong
to the dynamic part of the type of the object, not the static part.
We weren't up-casting to the dynamic type when we put the expression
together.
But other than that, I don't have Radars on any other problems with
generating valid expressions out of the local variable tree in Xcode.
Can you turn on the Xcode/gdb log (in Xcode 3.0 you do this in the
Debugging Pref Pane) and then generate the watch expression through
the UI that "makes gdb barf" and then file a bug with that log and the
correct expression you were typing in the console (or just type in in
the console, that will make its way into the log), and maybe we can
figure out why the UI isn't cons-ing up the correct expression?
Thanks,
Jim
_______________________________________________
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