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.
[ BUILD # : 200809220201 ] [ JDK VERSION : 1.6.0_07 ] try: https://java-nio-charset-enhanced.dev.java.net/source/browse/java-nio- charset-enhanced/trunk/test/sun/nio/cs/CharsetsTest.java?rev=410&view= markup
Created attachment 70616 [details] No local Variables with JUnit timeout option
Created attachment 70617 [details] No reasonable debug with JUnit timeout option
Created attachment 70618 [details] No reasonable debug with JUnit timeout option
I have downloaded the sources, started the debugger and when it stopped at the breakpoint, Local Variables displays just "this" which looks correct, there are no local variables defined in testDecoder() method till line 211. I'm not able to reproduce the problem from the first screenshot - problem with no current thread. Is this reproducible or did this happen just once? It's not clear to me what's wrong on the last screenshot. You have several threads stopped on the line breakpoint, green line is correct and content of Local Variables looks fine. Can you please elaborate on what do you mean by "No reasonable debug"?
Thanks for looking at this. I could reproduce it several times. Maybe your machine is faster than mine. ;-) Perhaps try with shorter time-out, to examine the first screen shot. 3rd screen shot was taken after a while. I could not reasonable single step in this case, too many threads were opened. Also Local Variables window was flickering and always changing. Maybe it will be possible, that NetBeans could stop JUnit timers in case of single step debug?
Ulf, there have been integrated some fixes and it seems to be resolved now. Could you please verify it in latest build?
Target milestone is 6.5, so I assume you don't mean 7.0 dev builds, am I right? Do you mean 6.5RC2 by "latest build"?
6.5RC and 7.0 dev builds are very similar regarding debugger functionality. Please try to verify if that works in 6.5RC. Thanks.
I have checked this issue with RC2, and experienced, that debug session now runs much more smoothly. :-) But there remains my proposal to stop JUnit timers during debugging, so I filed new Issue 153288.