[jdk21u] core dump on alpine, arm64, musl
solo turn
soloturn at gmail.com
Thu Oct 12 15:18:07 UTC 2023
hi,
i tried to open a bug in the bug tracker, but could not find a
possibility to log in, so excuse me trying to write here. on alpine
multiple jvm versions dump cure when doping gradle build which watches
the filesystem. the musl documentation says there is a difference with
signals:
https://wiki.musl-libc.org/functional-differences-from-glibc.html#Signal-mask-and-setjmp/longjmp
here links to stack traces:
https://github.com/gradle/gradle/issues/24875
https://github.com/gradle/native-platform/pull/283
copied text, from user bratkartoffel:
Using java 17 or later results in a more informative stacktrace. It
seems, that the _init from the library fails.
It can be easily reproduced with the gradle example project and a
simple ./gradlew clean. Setting the -Dorg.gradle.native=false does not
help.
hs_err_pid: https://tpaste.us/xyRo
Ref: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/50073
what is the best way to report this to jdk developers?
kind regards.
More information about the jdk-updates-dev
mailing list