-
Bug
-
Resolution: Won't Fix
-
P4
-
1.4.0, 1.4.1, 1.4.2, 5.0
-
generic, sparc
-
generic, solaris_7
Name: tb29552 Date: 06/14/2002
jdb starts up with a default exclude list of:
java.*,javax.*,sun.*,com.sun.*,
Since breakpoint requests do not have this filter added,
you can set and hit a breakpoint in one of those classes.
As soon as you try a step or next, the exclude filter added
to the EventRequest means you won't ever be notified of the
StepEvent (the back end will filter it out, as instructed).
The debugee program will act as if you had entered a cont
or resume instead of step/next. Somewhat surprising to the user.
It would be better for jdb to follow the principle of least
surprise and adjust the exclude list when a user shows interest
in a method by setting a breakpoint there. At the very least,
jdb should warn the user so they can change the exclude list
themselves.
======================================================================
- relates to
-
JDK-4497232 "step" doesn't stop at the next statement - it completes the program
-
- Closed
-
-
JDK-4725407 JDWP: JDI STEP_IN fails when stepping into excluded classes and back out again
-
- Closed
-