-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 1.4.0
-
Component/s: vm-legacy
-
beta2
-
generic, x86, sparc
-
generic, solaris_7, windows_nt
-
Verified
These tests do a single step but the debuggee appears to run to completion
instead of stopping after the step.
The tests are (and this isn't always 100% reproducable):
com/sun/jdi/AllLineLocations.java
com/sun/jdi/FilterMatch.java
com/sun/jdi/FilterNoMatch.java
com/sun/jdi/FinalizerTest.java
com/sun/jdi/LocationTest.java
com/sun/jdi/MethodEntryExitEvents.java
com/sun/jdi/PopSynchronousTest.java
com/sun/jdi/RepStep.java
com/sun/jdi/StepTest.java
instead of stopping after the step.
The tests are (and this isn't always 100% reproducable):
com/sun/jdi/AllLineLocations.java
com/sun/jdi/FilterMatch.java
com/sun/jdi/FilterNoMatch.java
com/sun/jdi/FinalizerTest.java
com/sun/jdi/LocationTest.java
com/sun/jdi/MethodEntryExitEvents.java
com/sun/jdi/PopSynchronousTest.java
com/sun/jdi/RepStep.java
com/sun/jdi/StepTest.java
- duplicates
-
JDK-4482460 MethodExitEvent is not received upon method invokation
-
- Closed
-
-
JDK-4490676 Stepping in the debugger acts as go
-
- Closed
-