-prof dtraceasm

Henri Tremblay henri.tremblay at gmail.com
Thu Jan 20 02:54:21 UTC 2022


Thanks a lot.

For the record, I used dtrace instead.
The result is not as fun as yours because I need to track the output while
running the process somewhere else.
I'm on the wrong computer but I think I did something like:

*dtrace -q -n 'syscall::open:entry { printf("%-16s
%-16s\n",execname,copyinstr(arg0)); }'*

and I now think that iosnoop would do the same.

Henri

P.S.: However, so far it seems it was looking where the file should be so
the problem is somewhere else.

On Wed, 5 Jan 2022 at 03:09, Aleksey Shipilev <shade at redhat.com> wrote:

> On 1/5/22 5:19 AM, Henri Tremblay wrote:
> > I'm trying -prof dtraceasm and sadly it works on Java 17, when
> > copying hsdis-amd64.dylib at the right place but not when I do the same
> > with Java 8 (putting it in  jre/lib/server). Silly, I know.
>
> My hsdis installation script does this to capture most locations:
>
> cp ~/Install/libhsdis-amd64.so jre/lib/amd64/server/libhsdis-amd64.so
> cp ~/Install/libhsdis-amd64.so lib/amd64/server/libhsdis-amd64.so
> cp ~/Install/libhsdis-amd64.so lib/server/libhsdis-amd64.so
> cp ~/Install/libhsdis-amd64.so lib/server/hsdis-amd64.so
>
> You could also run strace to see where the OS is looking for hsdis:
>   $ strace -f java -XX:+UnlockDiagnosticVMOptions -XX:+PrintAssembly 2>&1
> | grep hsdis
>
> --
> Thanks,
> -Aleksey
>
>


More information about the jmh-dev mailing list