Fix gai_strerror() thread-safety on Windows.
Commit 5579388d
removed code that supplied a fallback implementation of
getaddrinfo(), which was dead code on modern systems. One tiny piece of
the removed code was still doing something useful on Windows, though:
that OS's own gai_strerror()/gai_strerrorA() function returns a pointer
to a static buffer that it overwrites each time, so it's not
thread-safe. In rare circumstances, a multi-threaded client program
could get an incorrect or corrupted error message.
Restore the replacement gai_strerror() function, though now that it's
only for Windows we can put it into a win32-specific file and cut it
down to the errors that Windows documents. The error messages here are
taken from FreeBSD, because Windows' own messages seemed too verbose.
Back-patch to 16.
Reviewed-by: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Discussion: https://postgr.es/m/CA%2BhUKGKz%2BF9d2PTiXwfYV7qJw%2BWg2jzACgSDgPizUw7UG%3Di58A%40mail.gmail.com
This commit is contained in:
parent
e70abd67c3
commit
65f438471b
5 changed files with 61 additions and 0 deletions
|
@ -1885,6 +1885,7 @@ if test "$PORTNAME" = "win32"; then
|
|||
AC_LIBOBJ(win32env)
|
||||
AC_LIBOBJ(win32error)
|
||||
AC_LIBOBJ(win32fdatasync)
|
||||
AC_LIBOBJ(win32gai_strerror)
|
||||
AC_LIBOBJ(win32getrusage)
|
||||
AC_LIBOBJ(win32link)
|
||||
AC_LIBOBJ(win32ntdll)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue