Debugging segmentation faults in the JVM on linux-powerpc

John Paul Adrian Glaubitz glaubitz at
Sat Jun 10 22:18:28 UTC 2017

On 06/10/2017 11:57 PM, John Paul Adrian Glaubitz wrote:
> Thread 2 "jmod" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xf7f9f460 (LWP 19187)]
> StubGenerator::SafeFetch32 (adr=0xabc, errValue=2748) at ./src/hotspot/src/cpu/zero/vm/stubGenerator_zero.cpp:211
> 211         value = *adr;

>From the description of SafeFetch32():

// Safefetch allows to load a value from a location that's not known
// to be valid. If the load causes a fault, the error value is returned.

So, it seems SafeFetch32() is not able to properly determine whether
it's safe to read from a particular location and then causes a segfault
when trying to read from that location because it assumed that was


 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz at
`. `'   Freie Universitaet Berlin - glaubitz at
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

More information about the hotspot-dev mailing list