[Date Prev][Date Next]
Re: (ITS#6478) slapd crashes with segfault
> We managed to install it with debug-symbols now,
> but did not have a new crash (yet).
> However we did a deeper anaylysis of existing
> Here is the outcome:
> (gdb) thread 1
> [Switching to thread 1 (process 17895)]#0 0x00000037a4e30045 in raise ()
> rom /lib64/libc.so.6
> (gdb) bt
> #0 0x00000037a4e30045 in raise () from /lib64/libc.so.6
> #1 0x00000037a4e31ae0 in abort () from /lib64/libc.so.6
> #2 0x00000037a4e681bb in __libc_message () from /lib64/libc.so.6
> #3 0x00000037a4e6f444 in _int_free () from /lib64/libc.so.6
> #4 0x00000037a4e72a6c in free () from /lib64/libc.so.6
> #5 0x0000000000559e07 in sb_rdahead_remove (sbiod=3D0x2aaac488d0d0) at
I still see some inconsistencies: in sockbuf.c there's no call to free()
at line 606. So, either the core is inconsistent, or slapd was linking an
incorrect liblber, if at all possible.
Not sure how to proceeding in debugging this issue.