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.
NB 6.9 201005060200, JDk 6u20 Steps to reproduce: - run IDE - create simple class - push main menu Debugger | New Breakpoint - choose Breakpoint Type : Class .. Stop on Class Load or Unload - push Ok -> breakpoint is visible in Breakpoint window, but no sign of this breakpoint in editor (gutter)
This works for me in current dev build. Can you please check this again? I've tried to create class breakpoint on several different classes, even e.g. inner classes of java.util.HashMap. If you have a class where this does not work, please attach it here... Thanks.
Created attachment 99088 [details] screenshot
I am still able to reproduce it in NB 6.9 201005170932 - see attached screenshot, the class I use (MemoryView) is from project http://qa.netbeans.org/modules/debugger/promo-h/MemoryView.zip
Hmm, strange. I'm still not able to reproduce this in my own dev build. I'll try it in the official build #201005170932... Does it work when you add the class breakpoint via clicking into the gutter to the line of the class declaration?
Even in build #201005170932 it works fine for me...
(In reply to comment #4) > Hmm, strange. I'm still not able to reproduce this in my own dev build. I'll > try it in the official build #201005170932... > > Does it work when you add the class breakpoint via clicking into the gutter to > the line of the class declaration? Yes, it works in this way. (In reply to comment #5) > Even in build #201005170932 it works fine for me... Martin, I can turn-on some logging and attach it here if needed, just let me know. I am able to reproduce it for 100% (JDK 6u20 64b, Ubuntu 9.10 64b)
I'm changing the subject and changing to an enhancement. The problem was in submitting the breakpoint with a simple name instead of the full name which includes the package. Ideally, we should have a code-completion there for all class names that are known. And we should print a warning if the provided class name is not found on classpath.
(In reply to comment #7) > Ideally, we should have a code-completion there for all class names that are > known. Already fixed. Code completion is there (seen in NB73)
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost.
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost. This time the target milestone is really set.