stan/jdk-24
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

8131331: tmtools/jstack/locks/wait_interrupt and wait_notify fail due to wrong number of lock records

Browse Source 
Make new thread dump output line optional

Reviewed-by: dholmes
This commit is contained in:
Daniel D. Daugherty 2015-07-15 15:52:55 -07:00
parent ce283b1347
commit 6964787851
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
hotspot/src/share/vm/runtime/vframe.cpp
View File

@ -235,12 +235,14 @@ void javaVFrame::print_lock_info_on(outputStream* st, int frame_count) {
// disable the extra printing below. // disable the extra printing below.
mark = NULL; 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 // This is not the first frame so we either own this monitor
// or we owned the monitor before and called wait(). Because // or we owned the monitor before and called wait(). Because
// wait() could have been called on any monitor in a lower // wait() could have been called on any monitor in a lower
// numbered frame on the stack, we have to check all the // numbered frame on the stack, we have to check all the
// monitors on the list for this frame. // 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(); mark = monitor->owner()->mark();
if (mark->has_monitor() && if (mark->has_monitor() &&
( // we have marked ourself as pending on this monitor ( // we have marked ourself as pending on this monitor