Sybase ASA/Solaris 10/UltraSPARC core dumps

Classic Servoy
1

Hi all!

We’ve got an Sun Fire 280R (dual Ultra-SPARC III) with the latest Solaris 10 (update 3, 11/06) installed on it, nothing particularly special done with it.

I’ve installed Sybase ASA 9.2 but any executable in the bin directories immediately core dump, simply mentioning
“Abort (core dumped)”

using (for example) 64-bit dbtsinfo, truss excerpt:
resolvepath(“/platform/SUNW,Sun-Fire-280R/lib/sparcv9/libc_psr.so.1”, “/platform/sun4u-us3/lib/sparcv9/libc_psr.so.1”, 1023) = 45
open(“/platform/SUNW,Sun-Fire-280R/lib/sparcv9/libc_psr.so.1”, O_RDONLY) = 3
<>
mmap(0x00010000, 65536, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFFFFFFFF7D100000
sigaction(SIGPIPE, 0xFFFFFFFF7FFFF7D0, 0x00000000) = 0
Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFFFF7E539400
siginfo: SIGSEGV SEGV_MAPERR addr=0x4ABA50A05F8011CE
Received signal #11, SIGSEGV [caught]
siginfo: SIGSEGV SEGV_MAPERR addr=0x4ABA50A05F8011CE
After which the process starts dying.

32-bit output is a bit different, but the same error occurs:
resolvepath(“/platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1”, “/platform/sun4u-us3/lib/libc_psr.so.1”, 1023) = 37
open(“/platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1”, O_RDONLY) = 3
<>
open(“/platform/SUNW,Sun-Fire-280R/lib/libmd5_psr.so.1”, O_RDONLY) = 3
<>
munmap(0xFED70000, 8192) = 0
Incurred fault #6, FLTBOUNDS %pc = 0xFF130900
siginfo: SIGSEGV SEGV_MAPERR addr=0x00000008
Received signal #11, SIGSEGV [caught]
siginfo: SIGSEGV SEGV_MAPERR addr=0x00000008

Has anybody any idea how to proceed? I’ve got no idea what a FLTBOUNDS fault is or how to analyze/resolve it…

thanks in advance

2

The_Loeki:
I’ve installed Sybase ASA 9.2 but any executable in the bin directories immediately core dump, simply mentioning
“Abort (core dumped)”

Hi there,

Before running the binaries, did you “source” the file asa_config.sh? It’s located in (default) /opt/SQLAnywhere9/bin64. This file sets up the environment to properly run SQL Anywhere.

Regards,

Jose Ramos
Product Manager
Sybase iAnywhere

3

I did.

Without the LD_LIBRARY_PATH settings Sybase will just report that it can’t find some libraries and quit off.

However, in a very odd twist of unexpected behaviour, it turns out Sybase does this behaviour only on an SSH session.
Using the serial console the programs actually run fine :shock:
I’ve yet to come up with a plausible theory as to why this is :roll:

The only difference I can think off is that console is the only place where root is allowed to directly log in. All others must log in as a user, than su to root (and end up in exactly the same environment otherwise…)