Displaying 4 results from an estimated 4 matches for "ldap_mods_free".
2016 Mar 04
0
Segmentation Fault when trying to set root samba password, IPA as a backend
.../samba/bin/smbpasswd -a ldap04
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
New SMB password:
Retype new SMB password:
Added user ldap04.
Program received signal SIGSEGV, Segmentation fault.
0xb7137578 in ldap_mods_free () from /usr/lib/i386-linux-gnu/libldap_r-2.4.so.2
(gdb) bt
#0 0xb7137578 in ldap_mods_free ()
from /usr/lib/i386-linux-gnu/libldap_r-2.4.so.2
#1 0xb70d7a14 in ldapmod_destructor (mod=0x80028280)
at ../source3/lib/smbldap.c:266
#2 0xb7da7b54 in _talloc_free_internal (ptr=0x80028280,...
2016 Mar 04
2
Segmentation Fault when trying to set root samba password, IPA as a backend
On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote:
> On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote:
> > OK, here is the output:
>
> Can you try the attached (UNTESTED!) patch?
>
> Thanks,
Gna, should have at least compiled it....
New patch :-)
Volker
--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax:
2016 Mar 02
4
Segmentation Fault when trying to set root samba password, IPA as a backend
...s
==2408== Rerun with --leak-check=full to see details of leaked memory
==2408==
==2408== For counts of detected and suppressed errors, rerun with: -v
==2408== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Added user ldap02.
==2405== Invalid read of size 4
==2405== at 0x56AB52A: ldap_mods_free (in
/usr/lib/i386-linux-gnu/libldap_r-2.4.so.2.10.3)
==2405== by 0x5728963: ldapmod_destructor (smbldap.c:266)
==2405== by 0x4A61AA3: _talloc_free_internal (talloc.c:1046)
==2405== by 0x4A6287F: _talloc_free_children_internal (talloc.c:1525)
==2405== by 0x4A61C02: _talloc_free_internal...
2016 Mar 01
3
Segmentation Fault when trying to set root samba password, IPA as a backend
On 01/03/16 21:35, Garming Sam wrote:
> Hi Rowland,
>
> This new segfault seems unrelated to the previous one. It's probably
> something like a double free, which typically shouldn't be that hard to
> fix. If you try running the tool under valgrind, it should provide
> enough information to fix the issue.
>
>
> Cheers,
>
> Garming
>
Who or what is