This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Reproduced on: NB3.5, Arrow build 031024_1, NB trunk build 200311111900. JDK1.4.2, MDI. (This is a random bug. I am able to reproduce the problem very often, but not always.) Steps: 1. Download the test example "Test1.java". Its package is "examples.texteditor". 2. Place line breakpoint at lines 23, 28 and 32. 3. Start Test1 in debugger. 4. (Stops at line 23.) Choose Debugger/Continue. 5. (Stops at line 28.) Wait until all debugger views are completelly updated. Choose Debugger/Continue. 6. (Stops at line 32.) In the Local Variables, variable "test3" should be listed, but is not. 7. Invoke "Step Over". 8. The variable "test4" is listed in Local Variables, but "test3" is not. A screenshot of this situation is attached.
Created attachment 12116 [details] Test Example.
Created attachment 12117 [details] Screenshot.
Newly created local variable sometimes took the same memory slot as a variable that went out of scope (test3 --> cntr). Debugger in this case did not properly refresh its cache of locals. /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/LocalVariable .java,v <-- LocalVariable.java new revision: 1.5; previous revision: 1.4 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/JPDACallStack Frame.java,v <-- JPDACallStackFrame.java new revision: 1.32; previous revision: 1.31
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.