Bug 185826 - Class breakpoint with simple name does not work
Class breakpoint with simple name does not work
Status: NEW
Product: debugger
Classification: Unclassified
Component: Java
6.x
PC Linux
: P2 (vote)
: TBD
Assigned To: Martin Entlicher
issues@debugger
: USABILITY
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-10 09:17 UTC by Marian Mirilovic
Modified: 2012-12-17 19:00 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments
screenshot (222.29 KB, image/png)
2010-05-17 14:08 UTC, Marian Mirilovic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2010-05-10 09:17:32 UTC
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)
Comment 1 Martin Entlicher 2010-05-17 13:50:23 UTC
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.
Comment 2 Marian Mirilovic 2010-05-17 14:08:18 UTC
Created attachment 99088 [details]
screenshot
Comment 3 Marian Mirilovic 2010-05-17 14:10:12 UTC
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
Comment 4 Martin Entlicher 2010-05-17 16:15:22 UTC
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?
Comment 5 Martin Entlicher 2010-05-17 18:20:42 UTC
Even in build #201005170932 it works fine for me...
Comment 6 Marian Mirilovic 2010-05-18 07:24:07 UTC
(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)
Comment 7 Martin Entlicher 2010-05-18 09:15:47 UTC
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.
Comment 8 markiewb 2012-10-16 16:32:42 UTC
(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)
Comment 9 markiewb 2012-12-17 18:52:52 UTC
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost.
Comment 10 markiewb 2012-12-17 19:00:54 UTC
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.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo