RFR: 8278330: dump stack trace if the jvmti test nsk/jvmti/GetThreadState/thrstat002 is failed with wrong thread state
Serguei Spitsyn
sspitsyn at openjdk.java.net
Tue Dec 7 09:20:30 UTC 2021
This is a fix for sub-task of:
8271065: vmTestbase/nsk/jvmti/GetThreadState/thrstat002 still fails with "Wrong thread "thr1" (...) state after SuspendThread"
The vmTestbase/nsk/jvmti/GetThreadState/thrstat002 test is intermittently failing with the wrong thread state reported.
It is most likely because of the unexpected JFR (or NMT) activity.
In order to confirm this guess we need to dump the stack trace in a case of this failure.
-------------
Commit messages:
- fixed: 8278330 dump stack trace if the jvmti test nsk/jvmti/GetThreadState/thrstat002 is failed with wrong thread state
Changes: https://git.openjdk.java.net/jdk/pull/6735/files
Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=6735&range=00
Issue: https://bugs.openjdk.java.net/browse/JDK-8278330
Stats: 101 lines in 1 file changed: 101 ins; 0 del; 0 mod
Patch: https://git.openjdk.java.net/jdk/pull/6735.diff
Fetch: git fetch https://git.openjdk.java.net/jdk pull/6735/head:pull/6735
PR: https://git.openjdk.java.net/jdk/pull/6735
More information about the serviceability-dev
mailing list