libnl segfault in genl/mngt.c (prior to application's main())

[Thomas Graf]

On 11/21/12 at 12:37am, Timo Buhrmester wrote:
> In particular this is about kismet, a program using libnl, which segfaults
> right after launch, before even main() is called.
> It looks like libnl is responsible, here's what i did and some information:
> 
> # uname -a
> Linux fisted 3.6.6-gentoo12019 #1 SMP Tue Nov 20 06:07:13 CET 2012 x86_64
> AMD Athlon(tm) II Dual-Core M300 AuthenticAMD GNU/Linux
> 
> libnl3 version is 3.2.14, or 3.2.14:3, the latter might be something
> gentoo-specific.
> libnl1 version is libnl-1.1-r3
> i have no idea why kismet wants both, anyway.
> 
> # ldd ./kismet_server
[...]
>         libnl-genl-3.so.200 => /usr/lib64/libnl-genl-3.so.200
> (0x00007fa051ed2000)
>         libnl-3.so.200 => /usr/lib64/libnl-3.so.200 (0x00007fa051cb6000)
[...]
>         libnl.so.1 => /usr/lib64/libnl.so.1 (0x00007fa050d82000)

Linking to two different libnl versions at the same time is not
supported. They have partially compatible APIs which obviously
conflict so you have libnl1 symbols using libnl3 symbols. Therefore
the segfault.