[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[news.eclipse.tools.jdt] Re: JDT watchpoints are surprising
|
AH! Thank you.
"Darin Wright" <Darin_Wright@xxxxxxxxxx> wrote in message
news:f8qcfl$o0r$1@xxxxxxxxxxxxxxxxxxxx
> You can set the "watchpoint" to be an "instance breakpoint" using the
> "Instance Breakpoints..." action from the variables view. So when you stop
> at the watchpoint the first time, select the associated object in the
> varibles view (this), and use "Instance Breakpoints..." to restrict the
> breakpoint to that object.
>
> Darin Wright
>
> "Don Porges" <dporges@xxxxxxxxxxxxxxx> wrote in message
> news:f8o8lp$bl4$1@xxxxxxxxxxxxxxxxxxxx
>> Do I understand correctly that a JDT "watchpoint" applies to every
>> instance of the asked-for field name within a given class, and not only
>> the exact object that the user clicks on in the variable window? If so,
>> this seems like it would almost never be useful. (And it should be
>> explained in the docs, since I've never heard of a "watchpoint" that does
>> that, and I expect others will be confused as well.)
>>
>> Relatedly, can anything useful be done (in any context) with the "id"
>> that I see that every object is given, beyond writing it down and thus
>> getting a clue that two things are the same object, or not?
>>
>>
>
>