nxmibc segfaulting

[wwwiebe]

I'm attempting to install version 1.2.16 on Gentoo from source. Almost everything works, with the exception of nxmibc, which segfaults whenever it is run. I've tried running a simple 'nxmibc --help' manually and still see a Segfault. Has anyone come across an issue like this?

[victor]

Hi,

can you please run it under gdb and post backtrace after crash?

Best regards,
Victor

[wwwiebe]

Hi Victor, sure thing. Here's the output:

[root@ITBox:/opt/netxms/bin] [S1V: 5.4.RC3.0] [16:38:18] $ gdb ./nxmibc
GNU gdb (Gentoo 7.4 p1) 7.4
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
http://bugs.gentoo.org/...
Reading symbols from /opt/netxms/bin/nxmibc...done.
(gdb) run
Starting program: /opt/netxms/bin/nxmibc
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?

Program received signal SIGSEGV, Segmentation fault.
0x00000000006612a0 in strcmp@@GLIBC_2.2.5 ()
(gdb)

[alk]

Type "bt" on gdb prompt "(gdb)", this will produce complete backtrace

[wwwiebe]

Aha. Apologies. Here is the output:

(gdb) run
Starting program: /opt/netxms/bin/nxmibc --help
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?

Program received signal SIGSEGV, Segmentation fault.
0x00000000006612a0 in strcmp@@GLIBC_2.2.5 ()
(gdb) bt
#0  0x00000000006612a0 in strcmp@@GLIBC_2.2.5 ()
#1  0x00007ffff7de7356 in elf_machine_rela (sym=0x400af0, skip_ifunc=<optimized out>, reloc_addr_arg=0x7ffff6ef1950, version=<optimized out>, map=0x7ffff7fe0000, reloc=<optimized out>) at ../sysdeps/x86_64/dl-machine.h:302
#2  elf_dynamic_do_Rela (skip_ifunc=<optimized out>, lazy=<optimized out>, nrelative=<optimized out>, relsize=<optimized out>, reladdr=<optimized out>, map=0x7ffff7fe0000) at do-rel.h:146
#3  _dl_relocate_object (scope=0x7ffff7fe0358, reloc_mode=<optimized out>, consider_profiling=consider_profiling@entry=0) at dl-reloc.c:265
#4  0x00007ffff7dde3e0 in dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=0x7ffff7fdb740) at rtld.c:2282
#5  0x00007ffff7defb18 in _dl_sysdep_start (start_argptr=start_argptr@entry=0x7fffffffe1f0, dl_main=dl_main@entry=0x7ffff7ddcb60 <dl_main>) at ../elf/dl-sysdep.c:244
#6  0x00007ffff7ddfd45 in _dl_start_final (arg=0x7fffffffe1f0) at rtld.c:337
#7  _dl_start (arg=0x7fffffffe1f0) at rtld.c:563
#8  0x00007ffff7ddc598 in _start () from /lib64/ld-linux-x86-64.so.2
#9  0x0000000000000002 in ?? ()
#10 0x00007fffffffe470 in ?? ()
#11 0x00007fffffffe487 in ?? ()
#12 0x0000000000000000 in ?? ()
(gdb)

[victor]

Quite strange. Seems that crash occurs in process initialization, even before our code is called. That usually means that something is wrong with the libraries.

Best regards,
Victor

[wwwiebe]

I'll dig further with my sysadmin. Thanks!