[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: [10] RFR: 8185796: jstack and clhsdb jstack should show lock objects
From:       Yasumasa Suenaga <yasuenag () gmail ! com>
Date:       2017-10-09 14:19:50
Message-ID: 56759c30-f67c-3f1d-e056-70a090c916b0 () gmail ! com
[Download RAW message or body]

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://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 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 wrote:
> > > 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 contention?
> > > 
> > > You can take a look at any of the \
> > > hotspot/test/serviceability/sa/LingeredAppWith*.java files for this. The target \
> > > process does not have to be be fixed to LingeredApp -- in these \
> > > LingeredAppWith* cases, the targets are test-specific variations built on top \
> > > of LingeredApp for ease of implementation. 
> > > Thanks,
> > > Jini.


[prev in list] [next in list] [prev in thread] [next in thread]