On Mon, 14 Oct 2024 08:50:52 GMT, Afshin Zafari <azaf...@openjdk.org> wrote:
>> Why is this assert triggered? That sounds like a bug.
>
> The assertion that happens during building jdk-image:
>
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # Internal Error
> (/home/afshin/scratch/833XX_nmt_VMT_with_tree/src/hotspot/share/utilities/growableArray.hpp:142),
> pid=1234272, tid=1234278
> # assert(0 <= i && i < _len) failed: illegal index 0 for length 0
> #
> # JRE version: (24.0) (fastdebug build )
> # Java VM: OpenJDK 64-Bit Server VM (fastdebug
> 24-internal-2024-09-30-0937351.afshin..., mixed mode, emulated-client,
> tiered, compressed oops, compressed class ptrs, serial gc, linux-amd64)
> # Core dump will be written. Default location: Core dumps may be processed
> with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or
> dumping to /home/afshin/scratch/833XX_nmt_VMT_with_tree/make/core.1234272)
> #
> #
>
> --------------- S U M M A R Y ------------
>
> Command Line: -Denv.class.path=
> -Dapplication.home=/home/afshin/scratch/833XX_nmt_VMT_with_tree/build/linux-x64/jdk
> -Xms8m -XX:+UseSerialGC -Xms32M -Xmx512M -XX:TieredStopAtLevel=1
> -Djdk.module.main=jdk.jlink jdk.jlink/jdk.tools.jmod.Main create
> --module-version 24-internal --target-platform linux-amd64 --module-path
> /home/afshin/scratch/833XX_nmt_VMT_with_tree/build/linux-x64/images/jmods
> --libs
> /home/afshin/scratch/833XX_nmt_VMT_with_tree/build/linux-x64/support/modules_libs/jdk.sctp
> --class-path
> /home/afshin/scratch/833XX_nmt_VMT_with_tree/build/linux-x64/jdk/modules/jdk.sctp
> --legal-notices
> /home/afshin/scratch/833XX_nmt_VMT_with_tree/build/linux-x64/support/modules_legal/common
> --exclude **{_the.*,_*.marker*,*.diz,*.debuginfo,*.dSYM/**,*.dSYM}
> --compress zip-1 --date 2024-09-30T09:37:57Z
> /home/afshin/scratch/833XX_nmt_VMT_with_tree/build/linux-x64/support/images/jmods/jdk.sctp.jmod
>
> Host: afshin-Precision-7920-Tower, Intel(R) Xeon(R) Silver 4114 CPU @
> 2.20GHz, 40 cores, 62G, Ubuntu 20.04.6 LTS
> Time: Mon Oct 14 10:52:34 2024 CEST elapsed time: 0.002402 seconds (0d 0h 0m
> 0s)
>
> --------------- T H R E A D ---------------
>
> Current thread is native thread
>
> Stack: [0x00007ffa5243a000,0x00007ffa5253b000], sp=0x00007ffa52539390, free
> space=1020k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> V [libjvm.so+0x18df026] VMError::report_and_die(int, char const*, char
> const*, __va_list_tag*, Thread*, unsigned char*, void*, void*, char const*,
> int, unsigned long)+0x486 (growableArray.hpp:142)
> V [libjvm.so+0x18df870] VMError::report_and_die(Thread*, void*, char
> const*, int, char const*, char const*,...
OK, so there's a bug in the new VMT. You should be getting the command run so
that you can reproduce it in gdb. If not, you can add `LOG=cmdlines` as an
environment variable before building.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/20425#discussion_r1802521408
