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.
I couldn't find this reported, so I must not have searched correctly. But just in case... With the the 6.8 dailies, I frequently (almost every debugger stop), see at least one of these messages. Notice in the attached png that the same object correctly evaluates and then doesn't when it checks for toString. If I click to another stack frame, then back to this one (didn't execute anything) then usually different spots will have this error.
Created attachment 88794 [details] error screenshot
It happens occasionally to me as well. The problem seems to be in proper tracking of current call stack frame.
Fixed in changeset: 147707:6dafbec8ce2f http://hg.netbeans.org/main/rev/6dafbec8ce2f
I'm tempted to delay traveling a few days while this percolates to the dailies, just to get a chance to try it... ;-)
*** Issue 173960 has been marked as a duplicate of this issue. ***
Integrated into 'main-golden', will be available in build *200910091401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/6dafbec8ce2f User: mentlicher@netbeans.org Log: #173701 - Keep the current stack frame set until the current thread is resumed.
*** Issue 174222 has been marked as a duplicate of this issue. ***
*** Issue 175146 has been marked as a duplicate of this issue. ***