-
Bug
-
Resolution: Fixed
-
P3
-
5.0
-
b32
-
generic
-
generic
-
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 |
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
-