On 2/2/22 08:53, Abigail G wrote:
Whoops, looks like I made the zip wrong, this one should work:
https://0x0.st/oHxy.zip
So it looks like a GC crash:
# SIGSEGV (0xb) at pc=0x00007fa2ba719208, pid=29539, tid=29557
siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr:
0x0000000000000100
Current thread (0x00007fa2b4091800): GCTaskThread "GC Thread#0" [stack:
0x00007fa2b8c10000,0x00007fa2b8d10000] [id=29557]
If I was stuck with issue like this, I'll try the following:
*) Test the memory. Memory problems frequently manifest as GC bugs:
https://shipilev.net/jvm/test-your-memory/
*) Use fastdebug JDK as the boot JDK, looking for a reasonable assert instead of anonymous crash.
This probably requires building it first after configuring using --with-debug-level=fastdebug. You
said the build eventually succeeds, so a few tries might be in order.
*) Bootstrap JDK 13 build with JDK 13. AFAICS, the actual requirement for boot
JDK is 12..13.
Regardless, even if you find a bug in JDK 12, it is unlikely to get fixed, as no one maintains JDK
12. Azul maintains JDK 13, so depending on your luck of identifying the issue with JDK 13, I'd say
fixing JDK 13 might be possible.
--
Thanks,
-Aleksey
