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...
-- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Registry Administrators, which is the registrant for Debian. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
