The Samba-Bugzilla – Bug 5698
Unable to initiate share with userid, get *** glibc detected *** /usr/sbin/smbd: free(): invalid pointer: 0xb7fcb540 ***
Last modified: 2008-08-21 14:08:21 UTC
whenever I try to map to my home share, using my userid and password, I get:
*** glibc detected *** /usr/sbin/smbd: free(): invalid pointer: 0xb7fcb540 ***
======= Backtrace: =========
mapping to a different share as guest works fine.
running on opensuse 11.0. Problem exists with the samba 3.2.0 shipped with opensuse, and also with the 3.2.1 from http://us5.samba.org/samba/ftp/Binary_Packages/SuSE/STABLE/11.0/
i will attach log output as attachments.
Created attachment 3486 [details]
log.smbd output when error occurs
there were two connections made during this session; a successful one to \\unladen-swallow\dist as guest, and a failed one to \\unladen-swallow\wegscd as wegscd.
in spite of the comment at the bottom of the log, there was no core dump to attach.
Can you run this under valgrind and try and reproduce the problem ? If you don't have valgrind try setting the glibc environment variable :
Created attachment 3492 [details]
output from valgrind (incorrect, had a null smbpasswd file)
as requested by Jeremy
Created attachment 3493 [details]
Tried to reproduce the crash, but failed.
Your latest attachement is not valgrind output. Can you run
valgrind --tool=memcheck --log-file=/tmp/valgrind-log smbd
and send /tmp/valgrind-log. Please also compile smbd with -g so that we can see the line numbers of the crash.
Created attachment 3499 [details]
valgrind output. from 3.2.2 build, with -g. core file available.
note that this was built from 3.2.2 source!!!!!!
Ah, ok, thanks! We're trying to free() something that was allocated with talloc. Looking.
(In reply to comment #7)
> Ah, ok, thanks! We're trying to free() something that was allocated with
> talloc. Looking.
good. I have the 3.2.2 tree out there and ready to test; am willing to patch and retest.
Ok, spotted the problem here. Will have a fix shortly.
Created attachment 3501 [details]
Patch for mixup of TALLOC/malloc. Please let me know if this fixes the problem.
this indeed fixes the problem! do I mark the bug as resolved, or do you?
I will. Fixed post 3.2.2. Thanks a lot for your help in tracking this down !