Kurt Roeckx <[EMAIL PROTECTED]> writes:
>> If this is broken then it's probably not the only problem --- we rely on
>> sa.sa_family in other places.
> sa.sa_family is not the problem itself, the problem is that if
> you use getaddrinfo with AF_UNSPEC, you can get more than replies
> with more than
On Mon, Jun 09, 2003 at 10:09:20AM -0400, Tom Lane wrote:
> Kurt Roeckx <[EMAIL PROTECTED]> writes:
> > I just saw in the cvs web that you changed freeaddrinfo2 to not
> > have the hint af anymore, and use the one from the struct addrinfo
> > itself.
>
> > This can break things. If you called get
I just saw in the cvs web that you changed freeaddrinfo2 to not
have the hint af anymore, and use the one from the struct addrinfo
itself.
This can break things. If you called getaddrinfo2() with
AF_UNSPEC, the version from the system can return an AF_UNIX
socket. For instance glibc 2.1 will do
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> I just saw in the cvs web that you changed freeaddrinfo2 to not
> have the hint af anymore, and use the one from the struct addrinfo
> itself.
> This can break things. If you called getaddrinfo2() with
> AF_UNSPEC, the version from the system can return a
