[aarch64-port-dev ] -XX:CompileCommand=print causes core dump

[Andrew Haley]

On 06/23/2018 02:36 PM, Dave Nuechterlein wrote:
> I have a very simple maven based JMH test.  If I add
> -XX:+UnlockDiagnosticVMOptions -XX:CompileCommand=print,com.ampere.pipeline_int_mvn.generated.MyBenchmark_test_method_jmhTest::test_method_avgt_jmhStub
> To my command string, I get a core dump:
> 
> # Compiler replay data is saved as:
> # /home/dnuechte/java/pipeline_int_mvn/replay_pid22566.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.java.com/bugreport/crash.jsp
> #
> Current thread is 22577
> Dumping core ...
> Aborted
> 
> Should I submit a bug report like the spew suggests?  Or is there a different mechanism at this point in the project?

No, just send the info to this list.

> I built my own hsdis two different ways, neither works.  I built one with binutils 2.24, and one with 2.29.  Since there was a change in the interface between 2.24 and 2.29, the version with 2.29 needs a patch to hsdis.c
> 
>    /* Finish linking together the various callback blocks. */
>    app_data->dinfo.application_data = (void*) app_data;
> -  app_data->dfn = disassembler(native_bfd);
> +  app_data->dfn = disassembler(bfd_get_arch(native_bfd),
> +                              bfd_big_endian(native_bfd),
> +                              bfd_get_mach(native_bfd),
> +                              native_bfd);
>    app_data->dinfo.print_address_func = hsdis_print_address_func;
>    app_data->dinfo.read_memory_func = hsdis_read_memory_func;

I have no idea: my hsdis works just fine.  In what way doesn't it work?

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671