Created attachment 219276 [details] error report file (the core dump is too big : 145551360 bytes) In an Oracle VM (VirtualBox 6.1), running FreeBSD13 uname -a FreeBSD freebsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 e18fc94e525-c253475(main): Thu Oct 1 06:34:24 UTC 2020 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 zfs -V zfs-2.0.0-rc1_140_gab6a0e236 zfs-kmod-2.0.0-rc1_140_gab6a0e236 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000000080121c49a, pid=2984, tid=0x0000000000018726 # # JRE version: OpenJDK Runtime Environment (8.0_272-b10) (build 1.8.0_272-b10) # Java VM: OpenJDK 64-Bit Server VM (25.272-b10 mixed mode bsd-amd64 compressed oops) # Problematic frame: # C [libc.so.7+0x15d49a] unsigned long+0x10a # # Core dump written. Default location: /root/java.core # # An error report file with more information is saved as: # /root/hs_err_pid2984.log # # If you would like to submit a bug report, please visit: # https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Ports%20%26%20Packages&component=Individual%20Port(s)&short_desc=java/openjdk8%3A%20 # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Abort (core dumped)
Reply on an old issue. Sorry it didn't get any traction back then. According to the error report file in the attachment the program is reading a jar file when it crashes. Are you still able to supply this jar file? So others can reproduce the issue. I notice that you were running 13.0-CURRENT. This is not a release version so it is interesting if this can be reproduced on a more recent release.
Hi Ronald Indeed, this crash is too old (4 years ago) for me to find the context in which it was executed. The jar file launched in this crash is a java program that I developed but I didn't keep the state of the corresponding source files. The bug seems to be in the C run-time (libc.so) called by the JVM. Sorry I can't help you more. Bernard Béancourt
(In reply to Bernard Béancourt from comment #2) Thanks for your quick response. If similar issues appear we can always re-open this issue.