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.

Bug 8984 - Class names of breakpoints should be taken exactly.
Summary: Class names of breakpoints should be taken exactly.
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P3 major (vote)
Assignee: Marian Petras
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-12-22 15:14 UTC by Jan Stola
Modified: 2003-06-30 17:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Stola 2000-12-22 15:14:35 UTC 
Pilsen (build 001220_3) and Netbeans 93
---------------------------------------

Class names of Line, Method, Exception and Variable breakpoints
are considered as if they were regular expression with * at the end.
For example exception breakpoint on "j" stops on all exceptions
starting with "j" (e.g. java.lang.IOException).

The breakpoint should work only for classes whose names
exactly match the class name of the breakpoint.
Comment 1 Daniel Prusa 2001-02-13 07:53:59 UTC 
*** Bug 9571 has been marked as a duplicate of this bug. ***
Comment 2 Jan Jancura 2001-02-21 12:51:09 UTC 
Assigned
Comment 3 Jan Jancura 2001-02-21 12:56:26 UTC 
Assigned
Comment 4 Jan Chalupa 2001-03-12 08:58:55 UTC 
Version: 'Dev' -> 3.2
Comment 5 Marian Petras 2001-03-12 10:44:21 UTC 
Fixed together with bug #9102 (Breakpoint set to a line in innerclass of a
innerclass is not valid).
Comment 6 Marian Petras 2001-03-30 20:16:40 UTC 
Exact matching works well for classes generated with FastJavac.
Line breakpoints are also working well as they are specified mainly by a line
number, not by class name.

For classes generated with Javac the name matching is nearly exact. It works
well for all named (both outer and inner/nested) classes. Exact matching is not
possible for anonymous classes due to JDK bug #4431170. It is not possible to
distinguish between anonymous classes nested directly into the outermost classes
and anonymous classes nested into nested classes.
The current behaviour is as follows: If a user tries to set a breakpoint to the
outermost class then the debugger sets the breakpoint to all anonymous inner
classes (directly or indirectly) nested to the outermost class and to all
classes directly or indirectly nested to them. It is not possible to set a
breakpoint to an anonymous inner class nested to a named nested class until the
nested class itself is (directly or indirectly) nested into another anonymous
inner class. It is possible to set a line breakpoint instead as a workaround.
Comment 7 Jan Stola 2001-04-26 16:40:17 UTC 
Verified in Netbeans release 3.2 build 38.
Comment 8 Jan Chalupa 2001-05-05 21:25:03 UTC 
Target milestone -> 3.2
Comment 9 Marian Petras 2001-05-28 17:20:33 UTC 
Not fixed for method breakpoints with status "stop on all methods for given class".
Comment 10 Marian Petras 2001-05-30 14:50:15 UTC 
Fixed in the main trunk.

Changed method 'exec()' so that it filters MethodEntryEvent and MethodExitEvent,
too.
Also changed class filter in 'set()' in section for 'allMethods' from
"getClassName()" to "getClassName() + '*'" so that it does not rely on incorrect
behaviour of JDK 1.3.
Comment 11 Jan Stola 2001-06-07 10:27:57 UTC 
Verified in Netbeans build 205.
Comment 12 Quality Engineering 2003-06-30 17:31:09 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.