| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2051135 | 1.4.1 | Mandy Chung | P4 | Closed | Fixed | hopper |
The two debuggee threads just run simple loops, each containg a bkpt.
When run under jdb with next, next, next, ....
we should stop at each line of each loop with a StepEvent (or a Bkpt event).
In some cases, we don't get the StepEvents for one of the threads; it
just stops at the bkpt.
In other cases, we don't get either StepEvents or Bkpt events for
one of the threads; it just runs to completion.
To see this
cd /net/jano.sfbay/export/disk20/serviceability/ws/regressionTestsInWaiting
./DeferredStepTest.sh
Look at the comments in that file to see how to run it to
see each sympton.
When run under jdb with next, next, next, ....
we should stop at each line of each loop with a StepEvent (or a Bkpt event).
In some cases, we don't get the StepEvents for one of the threads; it
just stops at the bkpt.
In other cases, we don't get either StepEvents or Bkpt events for
one of the threads; it just runs to completion.
To see this
cd /net/jano.sfbay/export/disk20/serviceability/ws/regressionTestsInWaiting
./DeferredStepTest.sh
Look at the comments in that file to see how to run it to
see each sympton.
- backported by
-
JDK-2051135 Deferred StepRequests missed in multithreaded debuggee
-
- Closed
-
- duplicates
-
JDK-4548917 StepRequest.addClassFilter(ReferenceType) doesn't comply with specification
-
- Closed
-