Getting forked JVM details on the server side.

[Vladimir Ozerov]

Aleksey,

Thank for reviewing this.

BTW, usually there is no need to build hsdis for Windows by hand as it can
be downloaded from internet (but I do not know whether this is permitable
by license). What user DO have to build manually is JDK in case he want to
use symbols. It would be nice if OpenJDK had distributions with debug for
Windows (may be they exist, but I failed to find them).

Vladimir.

2015-02-12 23:19 GMT+03:00 Aleksey Shipilev <aleksey.shipilev at oracle.com>:

> On 02/10/2015 04:31 PM, Aleksey Shipilev wrote:
> > On 02/10/2015 04:20 PM, Vladimir Ozerov wrote:
> >> Ok, one more try :-)
> >
> > YES. It works now. I put your patch here:
> >  http://cr.openjdk.java.net/~shade/7901293/WinPerfAsmProfiler.patch.txt
>
> That's one good piece of engineering. I had to clean up a few things to
> match the internal architecture of JMH, and pushed:
>  http://hg.openjdk.java.net/code-tools/jmh/rev/61fd51cdd7eb
>
> Notably:
>  - Profiler is called "WinXperfAsmProfiler" now
>  - Handshake classes are gone, the binary link is more streamlined
>  - PID resolver is now working unconditionally over MXBeans
>
> Verified "-prof xperfasm" works on my Windows 7 Pro and self-built
> hsdis-amd64.
>
> Thanks a lot for contribution!
>
> Cheers,
> -Aleksey.
>
>