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.
This is possible UI defect. But feel free to change it to Enhancement. I used to be regular user of debugger, but I'm not anymore. Yesterday I decided to try debugger after long time and so I attached to running NB process. I must say I was nicely surpriced by the progress you did guys! Much better UI and everything worked very good. Slow, but very good. I promise I will use it more often now. The debugging process stopped at the breakpoint. I was evaluating some local variables. And I was curious which other views/functionality is there (stack, locals, threads, watches, etc.) and so I was looking around. I opened the thread view and was clicking on different threads to see what is this view good for, etc. Now after a few minutes I returned back to my breakpoint and wanted to continue in debugging. Unfortunately the Step action was disabled and after a moment I realized that I'm in bad thread. So I should return to the one which I was debugging last time. You will think I'm silly, but I was not able to do it - there was about 20 threads and I was not able to found the original one. After a few minutes and trying about 10 of them I simply stopped the debugging and started it again. I'm leaving decision about how typical this scenario/problem is on you. But in my case some badging of the thread I was debugging last time would be very helpful.
Current version of NB provides info abou thread name, which hit tha breakpoint, in Debugger Console.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.