8131331: tmtools/jstack/locks/wait_interrupt and wait_notify fail due to wrong number of lock records
Make new thread dump output line optional Reviewed-by: dholmes
This commit is contained in:
parent
ce283b1347
commit
6964787851
@ -235,12 +235,14 @@ void javaVFrame::print_lock_info_on(outputStream* st, int frame_count) {
|
||||
// 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
|
||||
|
Loading…
Reference in New Issue
Block a user