[Pkg-samba-maint] Bug#536640: Bug#536640: freeifaddrs crash

[Jelmer Vernooij]

Elie Rosenblum wrote:
>> Do you get the same backtrace that the original submitter was getting
>> (a
>> crash inside of freeifaddrs) ?
>>
>> Cheers,
>>
>> Jelmer
>>     
>
> Looks more straightforward from the samba log:
> [2009/08/01 03:20:47,  0] smbd/server.c:1068(main)
>   smbd version 3.4.0 started.
>   Copyright Andrew Tridgell and the Samba Team 1992-2009
> /usr/sbin/smbd: symbol lookup error: /usr/sbin/smbd: undefined symbol: _talloc_get_type_abort
>
> Linkage:
> raven:~# ldd /usr/sbin/smbd
>         linux-vdso.so.1 =>  (0x00007fffd01fe000)
>         libldap_r-2.4.so.2 => /usr/lib/libldap_r-2.4.so.2 (0x00007f64c7d81000)
>         liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x00007f64c7b72000)
>         libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00007f64c7944000)
>         libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00007f64c7687000)
>         libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00007f64c745c000)
>         libcom_err.so.2 => /lib/libcom_err.so.2 (0x00007f64c7259000)
>         libcups.so.2 => /usr/lib/libcups.so.2 (0x00007f64c701e000)
>         libgnutls.so.26 => /usr/lib/libgnutls.so.26 (0x00007f64c6d6c000)
>         libz.so.1 => /usr/lib/libz.so.1 (0x00007f64c6b55000)
>         libpthread.so.0 => /lib/libpthread.so.0 (0x00007f64c693a000)
>         libm.so.6 => /lib/libm.so.6 (0x00007f64c66b7000)
>         libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007f64c647f000)
>         libpam.so.0 => /lib/libpam.so.0 (0x00007f64c6274000)
>         libacl.so.1 => /lib/libacl.so.1 (0x00007f64c606d000)
>         libattr.so.1 => /lib/libattr.so.1 (0x00007f64c5e69000)
>         libcap.so.2 => /lib/libcap.so.2 (0x00007f64c5c65000)
>         libresolv.so.2 => /lib/libresolv.so.2 (0x00007f64c5a4e000)
>         libnsl.so.1 => /lib/libnsl.so.1 (0x00007f64c5836000)
>         libdl.so.2 => /lib/libdl.so.2 (0x00007f64c5632000)
>         libpopt.so.0 => /lib/libpopt.so.0 (0x00007f64c5429000)
>         libtalloc.so.1 => /usr/lib/libtalloc.so.1 (0x00007f64c5221000)
>         libwbclient.so.0 => /usr/lib/libwbclient.so.0 (0x00007f64c5015000)
>         libc.so.6 => /lib/libc.so.6 (0x00007f64c4cc4000)
>         libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00007f64c4aaa000)
>         libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00007f64c48a2000)
>         libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00007f64c46a0000)
>         /lib64/ld-linux-x86-64.so.2 (0x00007f64c7fcc000)
>         libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0x00007f64c4490000)
>         libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0x00007f64c421a000)
>         libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f64c4017000)
>
> Actually I just fixed it myself on the amd64 box by upgrading libtalloc1 from 1.2.1-1 to 1.3.1-2. Guess the samba 3.4.0 packages need to specify a minimum version of libtalloc1?
This was a bug in talloc that has since been fixed. This should be fixed
with the next upload of the Samba packages, when they'll be rebuilt
against a fixed version of talloc with proper symbol versioning.

Cheers,

Jelmer