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.
[dev-200503021900, JDK 1.5.0_02] During debugging simple loop where watch was set to control variable of the loop (i), red marking of changed watch was very unrealiable, simply said it was random.
Clarification: Value of the watch was sometimes red after change and sometimes not.
This issue was reported in NetCAT 4.1 program.
This behavior depends on time slice between two steps and is as designed in current version.
Very difficult to reproduce, but sometimes it really happens. Just reproduced couple minutes ago with changing String value.
There is no how to reproduce, so we can not fix it.
You just need to be consistent enough and try and try and try.
Hard to reproduce + not a big problem (bad color of some text somewhere) => P5 mkubec: You are simply not right. YOU should follow QA rules and fire a bugs with how to reproduce section.
jjancura: average developer would understand following paragraph: .. During debugging simple loop where watch was set to control variable of the loop (i), red marking of changed watch was very unrealiable .. simple loop is e.g. for (int i = 0; i < 20; i++) { } control variable of loop is 'i' and watch was created for this variable Debugging means using debugger and stepping by F8. Just read QE reports and you will learn lot of things and also how to reproduce bugs.
Doesn't seem to be reproducible.
Here is a simple test loop and instructions on how to use it. 1: StringBuilder sb = new StringBuffer(); 2: while (sb.length() < 600) 3: sb.append("abc 123 "); First start real slowly: Step to line 2. Step over to line 3. The sb should be plain. Step over to reach line 2. The sb should be bold. Step over to line 3. The sb should be plain. Now step over twice quickly. The sb should always be plain on line 3 but are very often bold. If it turns out plain then just step over twice quickly again.
As far as I know, the described behaviour is correct. When you are stepping slowly, everything works fine. But: 1) when you are stepping fast, the watches are not evaluated after each step (evaluation does not start immediatelly after step is done, but waits some small amount of time - to be able to step faster) 2) when watches are evaluated, the new value is compared to old displayed value. If they are not same, the value is marked as changed. It does not check, if value was changed during last step or not. This is simple help for you, to see, what changed since last valid status.
Verified.