socket_strerror() sometimes maps errno, instead of its argument
socket_strerror() sometimes maps errno, instead of its argument

Looks like a historical bug. Its err argument is an error number, but
if it isn't using a custom error message for it, it just calls
strerror() with the errno global, effectively ignoring its argument
and returning a semi-random string.

cjtallman/luasocket,BeamNG/luasocket,azukiapp/luasocket,BeamNG/luasocket,azukiapp/luasocket,cjtallman/luasocket,enginix/luasocket,BeamNG/luasocket,snegovick/luasocket,csteddy/luasocket,snegovick/luasocket,azukiapp/luasocket,cjtallman/luasocket,diegonehab/LuaSocket,fhaoquan/luasocket,masoudre11/luasocket,fhaoquan/luasocket,masoudre11/luasocket,bigcrush/luasocket,nmreis/luasocket,cjtallman/luasocket,nmreis/luasocket,csteddy/luasocket,enginix/luasocket,enginix/luasocket,StoneDot/luasocket,enginix/luasocket,masoudre11/luasocket,fhaoquan/luasocket,snegovick/luasocket,azukiapp/luasocket,csteddy/luasocket,bigcrush/luasocket,StoneDot/luasocket,bigcrush/luasocket,BeamNG/luasocket,StoneDot/luasocket,StoneDot/luasocket,nmreis/luasocket,diegonehab/LuaSocket,diegonehab/LuaSocket,azukiapp/luasocket