Product Version: NetBeans IDE 6.7 RC2 (Build 200906030001)
Java: 1.6.0_14; Java HotSpot(TM) Client VM 14.0-b16
System: Linux version 2.6.28-11-generic running on i386; UTF-8; en_US (nb)
If I create a fixed watch, it is not fixed in the Variables view - refreshes just like a regular watch. However, in the
Watches view it works correctly.
Steps to reproduce:
1) Open MemoryView -> MemoryView.java
2) toggle a breakpoint on line 101
3) create a watch 'new Long(free)' and create a fixed watch from it
4) Debug project
5) Open Variables view
6) Invoke Continue
7) Both watches (including the fixed one) are refreshed
8) Open Watches view
9) Invoke Continue
10) only the non-fixed watch is refreshed
Reproduced. There's something bad about how fixed watches are treated...
Happens when Watches are integrated in Variables.
after discussion with martin we decided to lower priority of this issue.
reason: fix is complicated and dangerous + there exists workaround
workaround: use watches window instead of variables window if you use fixed watches
=> p2 because of not working functionality. 67patch candidate.
Not a showstopper anymore.
The fixed watch is somehow broken by loading of local variables.
The fixed watch updates it's value even when watches are separated from Variables - when you switch to Variables and
then back to Watches.
Fixed in changeset: 134246:61e143cec540
Incorrect info in wiki:
67fixes1-candidate -> 67patch-candidate
Integrated into 'main-golden', will be available in build *200906110201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: Make the watch clon evaluated if the original was evaluated. This was found to be missing while exploring issue #166487.
Verified in trunk build. Will mark as verified once it's integrated to 67patch.
Marking as verified, so this can go to 67patch.
The fix has been ported into the release67_fixes repository.