Issues with dtraceasm, and a workaround

[Henri Tremblay]

Hi,

I can give it a spin. What would be the test script?
I try to benchmark something and if I see a nice layout with java code and
percentage I am happy?

On Thu, 18 Feb 2021 at 07:45, Aleksey Shipilev <shade at redhat.com> wrote:

> On 2/18/21 1:24 PM, Aleksey Shipilev wrote:
> > Hold on. So if we call Process.destroy, then we also close all the
> streams at the same time?
> >     https://bugs.openjdk.java.net/browse/JDK-8216990
> >
> > Whoa. So even the workaround above does not work reliably, as it races
> with the profiler process: if
> > we are lucky, profiler would succeed in dumping the output after the
> first SIGTERM, until
> > Process.destroy comes and closes everything. Hm.
>
> I do not have Mac OS to reproduce this, so can anyone else to give the
> following patch a spin on Mac
> OS and -prof dtraceasm?
>    https://github.com/openjdk/jmh/pull/22
>
> --
> Thanks,
> -Aleksey
>
>