Noticed that after I upgrade to the sp1 versions of the 2003 admin tools samba started faulting when I opened the active directory users & computers tool. The relevent part of the samba log is attached (sorry about the backtrace, no idea what I did to cause the binaries to be stripped, happy to rebuild) as is a tcpdump.
Created attachment 1742 [details] Relevent chunk of samba log
Created attachment 1743 [details] TCPdump of crash process
Any chance you can reproduce under GDB or valgrind? The 'stripped' look is as much a deficiency in glibc's backtrace code than anything else. Try -M single to make it run well under GDB or V.
(In reply to comment #3) > Any chance you can reproduce under GDB or valgrind? Yep, done #include <big-rant.h> Even rebuilt with -ggdb to try to get the most out of it. > The 'stripped' look is as much a deficiency in glibc's backtrace code than > anything else. Try -M single to make it run well under GDB or V. Using that as well. Program received signal SIGABRT, Aborted. 0xffffe410 in __kernel_vsyscall () (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0x40088885 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0x4008a002 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0x080abddf in talloc_chunk_from_ptr (ptr=0x869aab8) at lib/talloc/talloc.c:120 #4 0x080acb42 in talloc_steal (new_ctx=0x869eb98, ptr=0x869aab8) at lib/talloc/talloc.c:672 #5 0x082c7bf2 in ldapsrv_SearchRequest (call=0x86ba8e8) at ldap_server/ldap_backend.c:261 #6 0x082c9576 in ldapsrv_do_call (call=0x86ba8e8) at ldap_server/ldap_backend.c:730 #7 0x082c5d53 in ldapsrv_process_message (conn=0x86ce068, msg=0x869ad78) at ldap_server/ldap_server.c:85 #8 0x082c6174 in ldapsrv_decode_wrapped (conn=0x86ce068, blob={data = 0x0, length = 0}) at ldap_server/ldap_server.c:199 #9 0x082c6245 in ldapsrv_decode (private=0x86ce068, blob={data = 0x869d5c0 "O
Created attachment 1744 [details] TCPdump of crach proccess - updated - see packet #25, last packet before abort()
Created attachment 1745 [details] A valgrind log Decided this is irritating me enough to get a valgrind log, this seems much more useful then the gdb backtrace (at first glance).
I think this should be fixed in -r 13606.
Seems to fix the crash, but now there's a different error: "The Local Security Authotity could not be contacted"
After a fresh rebuild can confirm this is fixed.