Hi Nicolas,
Thank you for your help.
I agree that this behavior is disturbing. I also believed that getaddrinfo
should return at some point. But on that case, it never did.
I must say that it happened on one VM machine, and never reproduced on any
other machine. I haven't encountered this bug sin
Having getaddrinfo() not returning is disturbing. While it's true that all
of the OS' DNS resolution functions are synchronous, and will block until
the OS comes back with a response, it's usually expected that the OS
returns *eventually.* Either with an error (such as a timeout), or with
some
