-
Enhancement
-
Resolution: Fixed
-
P4
-
25
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8368608 | 21.0.10-oracle | Md Shahbaz Yusuf | P4 | Resolved | Fixed | master |
There were a number of changes in JDK-8356811 and JDK-8356588 that left a new Debuggee.classByName() call outside of any try block that would detect failures and force a call to quitDebuggee(). It was proven that this is technically not necessary (the test and debuggee still exit quickly and with a valid exception stack trace), but it would be good to clean up the cases that are easily fixed by extending the try clause up a few lines to before the classByName() call.
- backported by
-
JDK-8368608 Extend try block in nsk/jdi tests to capture exceptions thrown by Debuggee.classByName()
-
- Resolved
-
- relates to
-
JDK-8356588 Some nsk/jdi tests can fetch ThreadReference from static field in the debuggee: part 3
-
- Resolved
-
-
JDK-8356811 Some nsk/jdi tests can fetch ThreadReference from static field in the debuggee: part 4
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/14e41ab0
-
Review(master) openjdk/jdk/25337