SIGSEGV (0xb) at pc=0x4c8d4804e0c148f6, pid=46732, tid=0x00007faba7690700 about corretto-8 HOT 7 OPEN

Could you please help on this

from corretto-8.

Hi @anup60,
There is not enough information in the provided hs_err file to identify the root cause of the crash. Do you have more crash files?

In the hs_err file I see libraries which are not a part of corretto:

/usr/g/PET/lib64/linux2/libCalCfgFile.so
/usr/g/PET/lib64/linux2/libCalFile.so
/usr/g/PET/lib64/linux2/libCalUiUtil.so
/usr/g/PET/lib64/linux2/libDetCalCommon.so
/usr/g/PET/lib64/linux2/libErr.so
/usr/g/PET/lib64/linux2/libH5Wrap.so
/usr/g/PET/lib64/linux2/libRawPrimitives.so
/usr/g/PET/lib64/linux2/libRdfUtils.so
/usr/g/PET/lib64/linux2/libSipmGainCal.so
/usr/g/PET/lib64/linux2/libUniformCalFile.so
/usr/g/PET/lib64/linux2/libcfg.so
/usr/g/PET/lib64/linux2/libconfigMgr.so
/usr/g/PET/lib64/linux2/libdbUtils.so
/usr/g/PET/lib64/linux2/libfile.so
/usr/g/PET/lib64/linux2/libgebase2.so
/usr/g/PET/lib64/linux2/libobrivn.so
/usr/g/PET/lib64/linux2/libpetbase.so
/usr/g/PET/lib64/linux2/libpetlwc.so
/usr/g/PET/lib64/linux2/librdf.so
/usr/g/PET/lib64/linux2/librdfCpp.so
/usr/g/PET/parc/lib64/libhdf5.so.10.3.0
/usr/g/PET/parc/lib64/libhdf5_hl.so.10.2.0
/usr/g/ctuser/nuevo/lib64/libdbxi.so
/usr/g/ctuser/nuevo/lib64/libdbxnuevo.so
/usr/g/ctuser/nuevo/lib64/libdbxpg.so
/usr/g/ctuser/nuevo/lib64/libdbxtk.so
/usr/g/ctuser/nuevo/lib64/libdbxtri.so
/usr/g/ctuser/nuevo/lib64/libdmf.so
/usr/g/ctuser/nuevo/lib64/libdmfdicom.so
/usr/g/ctuser/nuevo/lib64/libicudata.so.42.1
/usr/g/ctuser/nuevo/lib64/libicui18n.so.42.1
/usr/g/ctuser/nuevo/lib64/libicuuc.so.42.1
/usr/g/ctuser/nuevo/lib64/libnvoer.so
/usr/g/ctuser/nuevo/lib64/libsslwrapper.so
/usr/g/ctuser/nuevo/lib64/libterrautil.so
/usr/g/ctuser/terra/lib64/libtca.so

Does you application or any your libraries use JNI? The crash might be originated from the native code.

from corretto-8.

Hi @eastig,

Thankyou for the update. When i debug using gdb I could see the failure is happening with the below library

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007fa476dcad20 in __pthread_clockjoin_ex () from /lib64/libpthread.so.0
Missing separate debuginfos, use: zypper install java-1.8.0-amazon-corretto-devel-debuginfo-1.8.0_382.b05-1.x86_64
(gdb) c
Continuing.

Thread 48 "Thread-3" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fa3b8e11700 (LWP 8028)]
0x00007fa46194dabd in ?? ()
(gdb) c
Continuing.
[Detaching after vfork from child process 10420]
[New Thread 0x7fa388d88700 (LWP 10421)]

Thread 48 "Thread-3" received signal SIGSEGV, Segmentation fault.
0x00007fa46137bcce in ?? ()
(gdb) c
Continuing.

Thread 48 "Thread-3" received signal SIGSEGV, Segmentation fault.
0x00007fa4762b2ee0 in os::print_hex_dump(outputStream*, unsigned char*, unsigned char*, int) () from /usr/java64/java-1.8.0-amazon-corretto/jre/lib/amd64/server/libjvm.so
(gdb) c
Continuing.

Thread 48 "Thread-3" received signal SIGABRT, Aborted.
0x00007fa4769f6c6b in raise () from /lib64/libc.so.6
(gdb) c
Continuing.

from corretto-8.

Hi @eastig,

Please see some more information.

Here we build this application in 32-bit java 1.8 jdk

Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) Server VM (build 25.201-b09, mixed mode)

and we run this application in 64 bit amazon corretto jvm

openjdk version "1.8.0_382"
OpenJDK Runtime Environment Corretto-8.382.05.1 (build 1.8.0_382-b05)
OpenJDK 64-Bit Server VM Corretto-8.382.05.1 (build 25.382-b05, mixed mode)

Is there any compatibility issue here

from corretto-8.

Is there any compatibility issue here

Nope.

BTW, you are using a very old build of Corretto 8: 8.382.05.1. The latest is 8.412.08.1. Can you try the latest one?

from corretto-8.