OpenJDK / bsd-port / jdk9 / hotspot
changeset 8708:d476f0841893
8131331: tmtools/jstack/locks/wait_interrupt and wait_notify fail due to wrong number of lock records
Summary: make new thread dump output line optional
Reviewed-by: dholmes
| author | dcubed |
|---|---|
| date | Wed, 15 Jul 2015 15:52:55 -0700 |
| parents | e4e4273e4c3f |
| children | d7342e80f950 |
| files | src/share/vm/runtime/vframe.cpp |
| diffstat | 1 files changed, 3 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/src/share/vm/runtime/vframe.cpp Wed Jul 15 10:37:11 2015 -0700 +++ b/src/share/vm/runtime/vframe.cpp Wed Jul 15 15:52:55 2015 -0700 @@ -235,12 +235,14 @@ // disable the extra printing below. mark = NULL; } - } else if (frame_count != 0) { + } else if (frame_count != 0 && ObjectMonitor::Knob_Verbose) { // This is not the first frame so we either own this monitor // or we owned the monitor before and called wait(). Because // wait() could have been called on any monitor in a lower // numbered frame on the stack, we have to check all the // monitors on the list for this frame. + // Note: Only enable this new output line in verbose mode + // since existing tests are not ready for it. mark = monitor->owner()->mark(); if (mark->has_monitor() && ( // we have marked ourself as pending on this monitor