Maarten Litmaath wrote:
> Ronald Starink wrote:
>
>>>> Tracing the edg-wl-ns daemon indicates that there is a segmentation
>>>> violation:
>>>>
>>>> [root@boszwijn root]# strace -Ff -p 3999
>>>> Process 3999 attached - interrupt to quit
>>>> futex(0x9c6fe9c, FUTEX_WAIT, 1, NULL) = -1 EINTR (Interrupted
>>>> system call)
>>>> +++ killed by SIGSEGV +++
>
> To get a stack trace, can you leave the debugger attached instead:
>
> gdb -p .....
Not exactly a stack trace:
Loaded symbols for /lib/tls/libpthread.so.0
Reading symbols from /lib/tls/libm.so.6...done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/libcrypt.so.1...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /opt/edg/lib/libedg_wl_classad_plugin.so...done.
Loaded symbols for /opt/edg/lib/libedg_wl_classad_plugin.so
0x00ea13ad in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/tls/libpthread.so.0
(gdb) finish
Run till exit from #0 0x00ea13ad in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/tls/libpthread.so.0
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 38517680 (LWP 19996)]
0x01026a75 in readdir64@@GLIBC_2.2 () from /lib/tls/libc.so.6
(gdb)
The library /lib/tls/libc.so.6 is a symlink and is just part of the
standard glibc package.
[root@boswachter root]# ls -l /lib/tls/libc*
-rwxr-xr-x 1 root root 1572412 Jan 12 2006
/lib/tls/libc-2.3.2.so
lrwxrwxrwx 1 root root 13 May 4 2006
/lib/tls/libc.so.6 -> libc-2.3.2.so
[root@boswachter root]# rpm -qf /lib/tls/libc.so.6 /lib/tls/libc-2.3.2.so
glibc-2.3.2-95.39
glibc-2.3.2-95.39
>
> Have there been any kernel parameter changes?
No, there were no changes to the kernel, its parameters, or glibc.
Ronald
|