From: nicolas@... Date: 2016-01-29T10:56:12+00:00 Subject: [ruby-core:73575] [Ruby trunk - Bug #12033] WSASocket can't work with Ruby extensions. Issue #12033 has been updated by Nicolas Noble. I forgot to mention that I tried this under windows 10 and Windows 7, with the same result on both os. ---------------------------------------- Bug #12033: WSASocket can't work with Ruby extensions. https://bugs.ruby-lang.org/issues/12033#change-56779 * Author: Nicolas Noble * Status: Open * Priority: Normal * Assignee: Nobuyoshi Nakada * ruby -v: ruby 2.2.3p173 (2015-08-18 revision 51636) [x64-mingw32] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- Basically, when creating a gem with C code that tries to do a WSASocket() call, the socket will end up being non-viable. I have tried this using the native DevKit compiler, rake-compiler-dock, ruby 2.2, 2.1, 32 and 64 bits, to no avail. If a C extension calls into socket(), that socket will work, but if it calls into WSASocket(), it somehow won't. I have attached an example of a very simple gem, which is basically the sample code from https://msdn.microsoft.com/en-us/library/windows/desktop/ms737550(v=vs.85).aspx In the first test, calling into socket() and binding that socket to localhost will work. In the second test, calling into WSASocket() will return a socket, but then binding it won't work, with a WSAENOTSOCK error. If you add a main() function that simply calls into the Init_foobar() function, and compile it into a normal exe file, both tests will work normally. My guess is that the ruby environment is doing something... weird ? And as a result, the winsock system is altered in a way that makes WSASocket unviable. ---Files-------------------------------- foobar.zip (2.68 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>