[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Seg Faults with ldapdelete (ITS#53)
All,
I also have this problem occurring in 1.1.4. I provide a backtrace
as well.
OSF1 V4.0
gdbm version 1.7.3.
non-SMP DEC Alpha
***backtrace
> ladebug /usr/local/libexec/slapd core
Welcome to the Ladebug Debugger Version 4.0-43
------------------
object file name: /usr/local/seth/libexec/slapd
core file name: core
Reading symbolic information ...done
Core file produced from executable slapd
Thread 0xa terminated at PC 0x3ff8058a118 by signal SEGV
(ladebug) where
>0 0x3ff8058a118 in nxm_thread_kill(0x14000e940, 0x0, 0x1a82a, 0x0,
0x3ff00000000, 0x3ff801775dc) DebugInformationStrippedFromFile92
#1 0x3ff80577950 in pthread_kill(0x3ff8055e508, 0x0, 0x140473e78,
0x140475980, 0x3ff00000000, 0x3ff805812c4)
DebugInformationStrippedFromFile80
#2 0x3ff8056c224 in UnknownProcedure3FromFile69(0x3ff8055dca0,
0x3ff00000009, 0x140473ac8, 0x3ff807b33d0, 0x1404735d8, 0x140473e78)
DebugInformationStrippedFromFile69
#3 0x3ff807b2178 in UnknownProcedure4FromFile1(0x1404735d8, 0x140473e78,
0x3ff807b3568, 0x0, 0x1404735d8, 0x3ff805812c4)
DebugInformationStrippedFromFile1
#4 0x3ff807b3564 in UnknownProcedure16FromFile1(0x140048440,
0x140473e78, 0x140473e78, 0x140472de0, 0xabadabad00beed00, 0x0)
DebugInformationStrippedFromFile1
#5 0x3ff807b35a4 in exc_unwind(0x140473e78, 0x140472de0,
0xabadabad00beed00, 0x0, 0x3ff807b3834, 0x410a4d4f00000011)
DebugInformationStrippedFromFile1
#6 0x3ff807b3830 in exc_raise_signal_exception(0x86, 0x0, 0x12002bd70,
0x1, 0x2, 0x0) DebugInformationStrippedFromFile3
#7 0x3ff805788b8 in UnknownProcedure6FromFile80(0x12002bd70, 0x1, 0x2,
0x0, 0x3ff800d5db4, 0x14002a358) DebugInformationStrippedFromFile80
#8 0x3ff800d5db0 in __sigtramp(0x2, 0x0, 0x3ff800d5db4, 0x14002a358,
0x140473638, 0x0) DebugInformationStrippedFromFile105
#9 0x12002bd70 in idl_delete_key(be=0x14003e060, db=0x14002a358,
key=struct { ... }, id=108586) idl.c:633
#10 0x12002dd8c in id2children_remove(be=0x14003e060, p=0x140045100,
e=0x140045580) id2children.c:86
#11 0x120025280 in ldbm_back_delete(be=0x14003e060, conn=0x140058980,
op=0x1404630a0, dn=0x140044f50="uid=1814500,o=pagemart.com") delete.c:108
#12 0x120016430 in do_delete(conn=0x140058980, op=0x1404630a0)
delete.c:77
#13 0x12000a0c4 in connection_operation(arg_v=0x140048360)
connection.c:58
#14 0x3ff805812c4 in thdBase(0x0, 0x0, 0x0, 0x1, 0x45586732, 0x3)
DebugInformationStrippedFromFile82
** End backtrace (hopefully outlook didn't munge any of this)
I configured it like so:
LDFLAGS="-L/usr/local/lib -lpthread
-lexc" CPPFLAGS="-I/usr/local/include" ./configure --with-ldbm-api=gdbm
$*
Hope this helps somewhat. I had attempted to trace this down
not too long ago and had found that the server was dumping
core in idl.c (ldap/servers/slapd/back-ldbm/idl.c) at
the following line in idl_delete_key.
if ( ! INDIRECT_BLOCK( idl ))
I never got any farther than this due to some other things that
sprang up (sorry).
I hope this helps, and I'll provide anything else needed.
-seth