From 66c296e27f980b4f1d2148d5a022314d23be2bb2 Mon Sep 17 00:00:00 2001 From: david Date: Thu, 6 Sep 2012 20:11:04 +0000 Subject: [PATCH] Use socket_strerror in Nsock callback traces. Otherwise WinSock error numbers are not understood; you get "Unknown error" instead of "Only one usage of each socket address (protocol/network address/port) is normally permitted." for example. --- nsock/src/nsock_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nsock/src/nsock_core.c b/nsock/src/nsock_core.c index 97b913b34..e4c8cda1b 100644 --- a/nsock/src/nsock_core.c +++ b/nsock/src/nsock_core.c @@ -1263,7 +1263,7 @@ void nsock_trace_handler_callback(mspool *ms, msevent *nse) { nsi = nse->iod; if (nse->status == NSE_STATUS_ERROR) - Snprintf(errstr, sizeof(errstr), "[%s (%d)] ", strerror(nse->errnum), nse->errnum); + Snprintf(errstr, sizeof(errstr), "[%s (%d)] ", socket_strerror(nse->errnum), nse->errnum); else errstr[0] = '\0';