process aborts (signal 6) with __sigenable

[Krishna R]

Hi,

Our application process crashes, when i check the stack trace of all threads in the core file, i see only the following as suspicious.

Can anyone please explain what this means?

Thread 9 (system thread 4131915):
#0 0xc000000000047810:0 in __sigenable+0x50 () from /usr/lib/hpux64/dld.so
#1 0xc00000000003d9c0:0 in apply_lazy_iplt_reloc+0x590 ()
from /usr/lib/hpux64/dld.so

[Dennis Handly]

This isn't the thread with the problem, the signal 6. What do the other threads look like?

[Krishna R]

All other threads are sleeping/waiting on condition variables...

These are the running threads: (obtained from the core file using gdb)

15 system thread 4131921 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1
13 system thread 4131919 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1
12 system thread 4131918 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1
10 system thread 4131916 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1
9 system thread 4131915 0xc000000000047810:0 in __sigenable+0x50 ()
from /usr/lib/hpux64/dld.so
7 system thread 4131908 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1
6 system thread 4131907 0xc00000000033d950:0 in _poll_sys+0x30 ()
from /usr/lib/hpux64/libc.so.1
5 system thread 4131906 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1
4 system thread 4131904 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1
3 system thread 4131903 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1
2 system thread 4131901 0xc00000000033e0d0:0 in _select_sys+0x30 ()
from /usr/lib/hpux64/libc.so.1
1 system thread 4131900 0xc00000000033ad50:0 in __ksleep+0x30 ()
from /usr/lib/hpux64/libc.so.1

[Dennis Handly]

>These are the running threads: (obtained from the core file using gdb)

Hmm, none of these look like they called abort. Did another process do a kill SIGABRT?

You might just give up on this and make sure you have the latest dld.so patch. There was a recent thread about a hang in apply_lazy_iplt_reloc.