Re: Possible GCC Bug?
Re: Possible GCC Bug?
- Subject: Re: Possible GCC Bug?
- From: "B.J. Buchalter" <email@hidden>
- Date: Wed, 9 Apr 2008 15:34:27 -0400
On Apr 8, 2008, at 23:34, Jack Repenning wrote:
On Apr 8, 2008, at 1:19 PM, B.J. Buchalter wrote:
I don't think GaurdMalloc will help much here, but using the Xcode/
GDB "watch variable" command (to enable a watchpoint) will. Set a
watchpoint on "fred" and Xcode will stop in the debugger on the
precise machine instruction that changes "fred".
Wait wait wait: that's actually what I was looking for when I
responded, but I can't find it in the Xcode (3.0) UI. Where's it
hiding?
Help->Search shows it at Run->Variables View->Watch Variable.
One more point about watch variables:
Xcode manages to confuse the hell out of gdb when you try to watch
(sufficiently nested) member variables, and the watch doesn't get set.
You can work around this by going into the gdb console and typing:
p &(this->path->to->my->member)
and then typing
watch *(address that gets printed from command above)
This has been very helpful in cases that the Xcode UI was not working
well...
Best regards,
B.J. Buchalter
Metric Halo
http://www.mhlabs.com
_______________________________________________
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