RE: Possible GCC Bug?
RE: Possible GCC Bug?
- Subject: RE: Possible GCC Bug?
- From: "Greg Knight" <email@hidden>
- Date: Wed, 9 Apr 2008 14:01:00 -0500
Hi Folks,
Thanks for your suggestions. The watch point helped me solve the problem. A
screen refresh triggered by DisposeWindow() was accessing my code in an
unexpected manner, and updating that variable. I'll have it fixed real soon.
Greg
-----Original Message-----
From: xcode-users-bounces+gregjknight=email@hidden
[mailto:xcode-users-bounces+gregjknight=email@hidden] On
Behalf Of Jens Ayton
Sent: Tuesday, April 08, 2008 6:16 PM
To: Jack Repenning; xcode-users Users
Subject: Re: Possible GCC Bug?
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.
--
Jens Ayton
Sed quis custodiet ipsos custodes?
_______________________________________________
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
_______________________________________________
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