Re: Xcode memory breakpoint - How?
Re: Xcode memory breakpoint - How?
- Subject: Re: Xcode memory breakpoint - How?
- From: James Bucanek <email@hidden>
- Date: Wed, 4 Jul 2007 10:37:57 -0700
Yves Poissant <mailto:email@hidden> wrote (Wednesday, July 4,
2007 8:57 AM -0400):
I have a instance of a class where one of its member variable
changes value. I placed a breakpoint wherever an instruction
might change its value but none of those breakpoint fire. I
want to watch this member variable during application
execution. So I set a watchpoint on that "m_figure" variable
when I break in the constructor. In the debugger variable
window, it looks like this:
Arguments
this
m_figure <<<<<<< This is who I want to watch.
However, when I click "Continue", I get the following message:
"Watchpoint 12 deleted in thread 1 - The program has left the block in which its expression is valid"
Variable watchpoints only persist for the duration of the
function call. Unfortunately, this makes them useless for 90% of
what you'd want to use them for. They're great for stopping a
big loop when something changes, but that's about it.
Consider a conditional breakpoint. Set the breakpoint in the
code where you suspect the problem is occurring, then make the
breakpoint conditional on some value (i.e. iVar!=good_value).
That might get you at least closer to the problem.
James Bucanek
____________________________________________________________________
Author of Beginning Xcode ISBN: 047175479X
<http://www.beginningxcode.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