Loading...

XML

Word

Printable

Type: Bug
Resolution: Not an Issue
Priority: P4
Fix Version/s: None
Affects Version/s: 21
Component/s: core-svc
Labels:
- loom
- noreg-self

Subcomponent:
debugger

The com/sun/jdi/JdbXXX tests rely on the jdb "threads" command output to find the main thread. If it is a virtual thread, it will not be included in the "threads" output unless the debuggee is run with -Djdk.trackAllThreads, so we need to make sure to include this option when launching the debuggee. The following tests are impacted.

com/sun/jdi/JdbMethodExitTest.java
com/sun/jdi/JdbStepTest.java
com/sun/jdi/JdbStopThreadTest.java
com/sun/jdi/JdbStopThreadidTest.java

Note that all these tests also fail due to ~~JDK-8309334~~, which needs to be fixed first. Also JdbMethodExitTest.java will fail due to ~~JDK-8309396~~, which should be fixed after this CR.

relates to

JDK-8309334 ProcessTools.main() does not properly set thread names when using the virtual thread wrapper

Resolved

JDK-8309396 com/sun/jdi/JdbMethodExitTest.java fails with virtual threads due to a bug in determining the main thread id

Resolved

JDK-8285422 [LOOM] Some com/sun/jdi test are failing with the vthread wrapper

Closed

links to

Review openjdk/jdk/14293

Assignee:: Chris Plummer

Reporter:: Chris Plummer

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2023-06-02 14:02

Updated:: 2023-06-05 17:38

Resolved:: 2023-06-05 17:38

Details

Description

Attachments

Issue Links

Activity

People

Dates