Debugging segmentation faults in the JVM on linux-powerpc

Andrew Haley aph at
Mon Jun 12 12:22:53 UTC 2017

On 12/06/17 13:08, Thomas Stüfe wrote:
> I agree with Severin. It makes sense to rule out a compiler failure before
> spending more work on it. The coding in question is completely architecture
> independent, and the fact that it only happens on one platform, and that
> the error vanishes in slowdebug, is suspicious.

Not necessarily.  The problem seems to be that we get a failure when
allocating a direct byte bufer, in Bits.reserveMemory().  The limit is
controlled by -XX:MaxDirectMemorySize.

It might well be a bug in the Zero interpreter.  I'd start by adding a
couple of lines in Bits.tryReserveMemory() to print out the
totalCapacity when allocation fails.

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the hotspot-dev mailing list