Red Hat Bugzilla – Bug 458790
libsmbclient segfaults with more than one SMBCCTX
Last modified: 2009-02-03 13:27:06 EST
Created attachment 314082 [details]
Description of problem:
The attached program segfaults.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
make testsmbclient CFLAGS=-g LDFLAGS=-lsmbclient
Segfaults in smbc_init_context at libsmb/libsmb_context.c:587.
Exits with status code 0.
Works fine in Fedora 9 with libsmbclient-3.2.0-2.17.fc9.x86_64.
Tracked this down using git bisect to this commit:
Author: Andreas Schneider <firstname.lastname@example.org>
Date: Tue Jul 15 14:57:32 2008 +0200
Release still reachable memory if the smbclient context is freed.
Signed-off-by: Andreas Schneider <email@example.com>
(cherry picked from commit 88c9cf2fdc8f3d704f7f27c25ef6dc6940d451d3)
Looks to me like that commit is just wrong. With that change in, when two contexts have been created and one is freed, resources still needed by the second will also be freed.
*** Bug 462403 has been marked as a duplicate of this bug. ***
This fix went into 3.2.2 -- is there any way we could get that into the Fedora 10 beta?
I tried samba-3.2.4-0.22.fc10.x86_64 and I am able to connect to Windows printers again.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here: