[aarch64-port-dev ] Sporadic crashes on aarch64 after switching from OpenJDK 9 to 10

Aleksey Shipilev shade at redhat.com
Wed Jun 20 06:27:04 UTC 2018


On 06/20/2018 08:16 AM, Stephan Bergmann wrote:
>> That's a safepoint SEGV.  It's deliberate.  If you step at that
>> point you'll enter the safepoint code.

...

>> What exactly is the failure?
> 
> The failure is that the process (running a C++ cppunittester executable, with an in-process
> instantiated JVM) terminates due to a SIGSEGV.  When inspecting the generated core file with gdb, it
> claims the above thread caused that "fatal" SIGSEGV.

My first bet would be that cpuunittester had installed its own signal handlers that overwrote JVM's
SEGV handlers that are required for normal operation. You would need to use jsig to make JVM work in
that config, see:
  https://docs.oracle.com/javase/8/docs/technotes/guides/vm/signal-chaining.html

-Aleksey



More information about the aarch64-port-dev mailing list