[Unbound-users] unbound segfaults
wouter at nlnetlabs.nl
Tue Apr 9 08:40:54 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
The bug has been fixed in svn trunk. Thanks for the report!
No official releases suffer from this issue, the segfault was caused
by an error in a bugfix that has not been released yet.
On 04/03/2013 11:37 PM, Chris Smith wrote:
> On Wed, Apr 3, 2013 at 5:26 PM, W.C.A. Wijngaards
> <wouter at nlnetlabs.nl> wrote:
>> I suspect two changes of causing it (I am supposedly on holiday,
>> so I'll make it short). The first is a binary API version change
>> in libunbound; this should likely not affect you, but if your
>> install is not 'clean', it could be that you now have two
>> libunbound.so.x versions, and if you compile with
>> --export-all-symbols then this could cause segfaults in the
>> unbound daemon if it picks the wrong library out of your libdir.
> Only one version - libunbound.so.2.2.1
>> The other is a codechange, to do with private-address
>> functionality; are you using private-address? This is the only
>> real codechange in this timeframe, and touches on a lot of
>> pointers... I thought it was fine, but then you always do until
>> you find the bug :-)
> Yes, using private-addresses!
>> That would be this patch that then causes the issue: svn diff
>> http://unbound.net/svn/trunk/iterator -r2867:2868 > file this
>> code does fire even if you do not have private-addresses
>> configured, but it does not seem to fail in unit tests. patch -r
>> reverses the patch if you want to try that.
> I'll give this a try.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the Unbound-users