Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 7
Affects Version/s: 5.0
Component/s: core-svc
Labels:

Subcomponent:
debugger
Resolved In Build:
b32
CPU:

generic
OS:

generic
Verification:
Verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2164857	6u10	James Holmlund	P3	Resolved	Fixed	b31
JDK-2185797	OpenJDK6	Kelly Ohair	P3	Resolved	Fixed	b18

When a thread is resumed, the call stack frames are invalidated.
The problem is, however, that not only frames of the resumed thread, but also frames of all other suspended threads are invalidated.
This bug is reproduced by the following new JTREG test:

com/sun/jdi/ResumeOneThreadTest.java

backported by

JDK-2164857 Thread resume invalidates all stack frames, even from other threads

Resolved

JDK-2185797 Thread resume invalidates all stack frames, even from other threads

Resolved

relates to

JDK-6701700 MonitorInfo objects aren't invalidated when the owning thread is resumed

Closed

JDK-6644945 "InvalidStackFrameException: Thread has been resumed" failure on Linux

Closed

JDK-2166391 MonitorInfo objects aren't invalidated when the owning thread is resumed

Resolved

JDK-6751643 ThreadReference.ownedMonitors() can return null

Closed

JDK-6865514 MonitorFrameInfo.java fails in 6u11

Closed

(2 relates to)

Assignee:: James Holmlund (Inactive)

Reporter:: Martin Entlicher

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 2008-05-12 13:35

Updated:: 2012-10-01 10:11

Resolved:: 2011-03-07 20:46

Imported:: 16/Sep/12 1:17 PM

Indexed:: 18/Jul/12 8:06 AM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates