Backtrace for Java thread at early JVM startup - was: Hotspot segfaulting on Linux SPARC

[John Paul Adrian Glaubitz]

Hello Michael!

On 04/15/2018 02:39 PM, Michael Dardis wrote:
> The invalid value is 0xabababab in hexadecimal.
> In debug builds this option is set: https://github.com/md-5/OpenJDK/blob/1415df45a29a0a0c56adf1271786e41d5f93ca57/src/hotspot/share/runtime/globals.hpp#L905
> Which causes freed memory to be filled with 0xabababab upon clearing.

This is a very useful information. I now know what to look for.

> Probably a memory bounds issue with access above or below the correct memory chunk.
> Unfortunately I can't provide further help, but hopefully that answers your question of where it's coming from.

Thanks a lot. I actually learned today that there is a regression in
the current Linux kernel version on sparc64 which can cause memory
corruption in userland. I have updated the kernel to a version which
carries a fix for it. Let's see if that helps.

Adrian

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