JVM crashed when attempting to load native binaries on SUSE

Question

Hello!
We have a java application that calls at some point C++ code in form of specific OS binaries. We tested for RedHat and SUSE - for the first OS it worked fine but for SUSE I got:
{color:#ff0000}#
# A fatal error has been detected by the Java Runtime Environment:
# SIGFPE (0x8) at pc=0xf7f4a1fb, pid=21443, tid=4149328800
# JRE version: 6.0_14-b08
# Java VM: Java HotSpot(TM) Client VM (14.0-b16 mixed mode linux-x86 )
# Problematic frame:
# C [ld-linux.so.2+0x91fb]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
T H R E A D
Current thread (0x08059000): JavaThread "main" [_thread_in_native, id=21448, stack(0xf749b000,0xf751c000)]
siginfo:si_signo=SIGFPE: si_errno=0, si_code=1 (FPE_INTDIV), si_addr=0xf7f4a1fb
Registers:
EAX=0x0df0d414, EBX=0xf7f5bff4, ECX=0x093522b0, EDX=0x00000000
ESP=0xf7517b84, EBP=0xf7517be0, ESI=0x0935245c, EDI=0xf7517c6c
EIP=0xf7f4a1fb, CR2=0xf7f33100, EFLAGS=0x00010246
Top of Stack: (sp=0xf7517b84)
0xf7517b84: ea91ab8b dc5cdb74 00000009 f7f04164
0xf7517b94: dc5ccb9c 0df0d414 dc5cdb74 f7f4e389
0xf7517ba4: 00000008 093522b0 dc5cb3ec dc5cdafc
0xf7517bb4: dc5d4030 00000000 00000000 09053344
0xf7517bc4: f7f5bff4 f7517ca0 dc5d3fb6 f7517c6c
0xf7517bd4: f7f5bff4 0935245c f7517c6c f7517c80
0xf7517be4: f7f4a587 f7517c6c 09352408 00000000
0xf7517bf4: 00000000 00000001 00000000 00000000
Instructions: (pc=0xf7f4a1fb)
0xf7f4a1eb: 8b 8a 94 01 00 00 8b 45 b8 89 4d d4 89 d1 31 d2
0xf7f4a1fb: f7 b1 6c 01 00 00 8b 81 70 01 00 00 8b 3c 90 85
Stack: [0xf749b000,0xf751c000], sp=0xf7517b84, free space=498k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ld-linux.so.2+0x91fb]
C [ld-linux.so.2+0x9587]
C [ld-linux.so.2+0xabff]
C [ld-linux.so.2+0x11471]
C [ld-linux.so.2+0xd3a6]
C [ld-linux.so.2+0x10cb9]
C [libdl.so.2+0xe4d]
C [ld-linux.so.2+0xd3a6]
C [libdl.so.2+0x12fc]
C [libdl.so.2+0xd84] dlopen+0x44
V [libjvm.so+0x3237c9]
V [libjvm.so+0x288819]
C [libjava.so+0xbcac] Java_java_lang_ClassLoader_00024NativeLibrary_load+0x6c
j java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/String;)V+0
j java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/io/File;)Z+300
j java.lang.ClassLoader.loadLibrary(Ljava/lang/Class;Ljava/lang/String;Z)V+127
j java.lang.Runtime.load0(Ljava/lang/Class;Ljava/lang/String;)V+57
j java.lang.System.load(Ljava/lang/String;)V+7
j com.boss.media.util.DllUtils.LoadNativeDll(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;+404
j com.boss.media.engine.StreamingEngine.getInstance(Ljava/lang/String;)Lcom/boss/media/engine/StreamingEngine;+9
{color:#000000}
Seems the crash is producing when Suse's ld-linux.so attempts to load our binaries.{color}
{color}{color:#000000}Does anyone have any idea on what is wrong here?
Thank you very much
With best regards,
Sorin
{color}

Answer 1

We tested for RedHat and SUSE - for the first OS it worked fine but for SUSE I got:Either the standard pointer problems leading to a spurious error or some subtle OS difference.
SIGFPEThat is a pretty specific signal. If the C++ code is not mucking around with numerics then it would suggest a pointer problem. If numerics are involved then that would be the first place to start (noting again that pointer problems can cause spurious errors.)