I guess it seldomly happens on linux and that's why it wasn't found before.
He used Solaris to notice it.

I took the opportunity to rewrite the Curl_connecthost() slightly to feature
less duplicate code in the two different versions (ipv4/ipv6).

hogs Windows machines when libcurl is being used multi-threaded (with > ~50
threads). Andrew Fuller helped us verify and test this.

According to a MSDN web page on connect(), it returns 0 when the connect
is done and thus we don't need the getsockopt() call anyway on Windows.

  addresses, if one of them fails (ipv4-code).

Jeremy Friesner.

build libcurl to use ares for asynch name resolves.

the define accordingly in the hostip.h header to work nicely all over.

name isn't an ip address

in the Curl_is_connected() function.

even better (also based on input from Martin).

AIX 3.2.5 and possibly other OSF-like system headers.

and this has been verified to correct the problem.

stack. Kjetil Jacobsen reported and verified the fix.

#651464.

or not

multi interface works with file:// URLs fine (previously it crashed). This
won't make it work on Windows though...

counter so that the caller needs to decrease that counter when done with
the returned data.

If compiled with MALLOCDEBUG I've added some extra checking that the counter
is decreased before a handle is closed etc.

interface

when talking to a IPv6-server using IPv6 IP address only.

the initial connect to "come through".

This should work fine for connect and for FTP-PASV connects. Needs massive
testing.

any name resolved data in any curl handle struct. That way, we won't mind
if the cache entries are pruned for the next time we need them. We'll just
resolve them again instead.

This changes the Curl_resolv() proto. It modifies the SessionHandle struct
but perhaps most importantly, it'll make the internals somewhat dependent
on the DNS cache not being disabled as that will cripple operations somewhat.
Especially for persistant connections.

now have --interface working properly

connect() so that it tells to which host and what port it is about to
attempt the connection