Hi all,
I uploaded new webrev to be adapted to current jdk10/hs:
http://cr.openjdk.java.net/~ysuenaga/JDK-8185796/webrev.03/
Please review and sponsor it.
Thanks,
Yasumasa
On 2017/09/27 0:31, Yasumasa Suenaga wrote:
Hi all,
I uploaded new webrev to be adapted to jdk10/hs:
http://c
Hi all,
I uploaded new webrev to be adapted to jdk10/hs:
http://cr.openjdk.java.net/~ysuenaga/JDK-8185796/webrev.02/
Thanks,
Yasumasa
On 2017/08/24 22:59, Yasumasa Suenaga wrote:
Thanks Jini!
I uploaded new webrev:
http://cr.openjdk.java.net/~ysuenaga/JDK-8185796/webrev.01/
This we
Thanks Jini!
I uploaded new webrev:
http://cr.openjdk.java.net/~ysuenaga/JDK-8185796/webrev.01/
This webrev has been ported print_lock_info() to JavaVFrame.java, and I've
added new testcase for `jhsdb jstack` and jstack command on `jhsdb clhsdb`.
Yasumasa
On 2017/08/24 18:01, Jini George
Apologize for the late reply, Yasumasa.
I think so, but I guess it is difficult.
For example, test for CLHSDB command is provided as
test/serviceability/sa/TestPrintMdo.java .
But target process seems to be fixed to "LingeredApp".
Can we change it to another program which generates lock conte
Hi Jini,
Thank you for your suggestion.
This is helpful, but looks like 'locked' is printed even when a thread
is waiting for the monitor entry, or has unlocked a lock.
IMHO we have to implement getPendingMonitor() and print_lock_info() in
JavaVFrame.java:
http://hg.openjdk.java.net/jdk1
Hi Yasumasa,
This is helpful, but looks like 'locked' is printed even when a thread
is waiting for the monitor entry, or has unlocked a lock. For a simple
test program, we would have:
"Thread-1" #11 prio=5 tid=0x7f393845 nid=0x6be4 waiting for
monitor entry [0x7f391501]
j
