Hmm, so the problem still lies in the ipv6 support patch from debian, but is not fixed by fixing the host && addr code flow. Probably your use case (usage through xinetd) hits code that triggered the assertion (host or addr is null) but will also trigger further failure...
Hmm, so the problem still lies in the ipv6 support patch from debian, but is not fixed by fixing the host && addr code flow. Probably your use case (usage through xinetd) hits code that triggered the assertion (host or addr is null) but will also trigger further failure...