Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 25
Affects Version/s: 25
Component/s: core-svc
Labels:

Subcomponent:
debugger
Resolved In Build:
b21

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8367089	21.0.10	Goetz Lindenmaier	P4	Resolved	Fixed	b01
JDK-8358936	21.0.9-oracle	Rashmi Biswal Biswal	P4	Resolved	Fixed	b01

In an effort go get rid of calls to Debugee.threadByName() or Debugee.threadByNameOrThrow(), I found that many tests store the thread being looked up in a static field of the debuggee. The test can fetch the ThreadReference from the static field instead of looking it up using APIs that rely on vm.allThreads().

backported by

JDK-8358936 Some nsk/jdi tests can fetch ThreadReference from static field in the debuggee

Resolved

JDK-8367089 Some nsk/jdi tests can fetch ThreadReference from static field in the debuggee

Resolved

relates to

JDK-8356823 Some nsk/jdi tests can fetch ThreadReference from static array field in the debuggee

Open

JDK-8356023 Some nsk/jdi tests can fetch ThreadReference from static field in the debuggee: part 2

Resolved

JDK-8356588 Some nsk/jdi tests can fetch ThreadReference from static field in the debuggee: part 3

Resolved

JDK-8353955 nsk/jdi tests should be fixed to not always require includevirtualthreads=y

Resolved

links to

Commit(master) openjdk/jdk21u-dev/d4b91ad7

Commit(master) openjdk/jdk/50145bb7

Review(master) openjdk/jdk21u-dev/2146

Review(master) openjdk/jdk/24935

(1 relates to, 4 links to)

Assignee:: Chris Plummer
Reporter:: Chris Plummer
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: 2025-04-28 11:23
Updated:: 2025-09-08 03:48
Resolved:: 2025-04-30 10:17

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates