[Bug 30815] Can't create winsock on Proteus ISIS for remote controll through mplabX

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Jun 1 11:33:50 CDT 2012


http://bugs.winehq.org/show_bug.cgi?id=30815

--- Comment #11 from Dan Kegel <dank at kegel.com> 2012-06-01 11:33:50 CDT ---
Created attachment 40362
  --> http://bugs.winehq.org/attachment.cgi?id=40362
More verbose version

Try this one, it's a bit more verbose.  With it, I see

trace:winsock:WSAStartup verReq=2
trace:winsock:WSAStartup succeeded
trace:winsock:WS_socket af=2 type=0 protocol=0
trace:winsock:WSASocketA af=2 type=0 protocol=0 protocol_info=(nil) group=0
flags=0x1
trace:winsock:WSASocketW af=2 type=0 protocol=0 protocol_info=(nil) group=0
flags=0x1
fixme:winsock:WSASocketW Defaulting to SOCK_STREAM
trace:winsock:WSASocketW     created 00bc
trace:winsock:WS_bind socket 00bc, ptr 0x89f6e4 { family AF_INET, address
0.0.0.0, port 8000 }, length 16
trace:winsock:WS_listen socket 00bc, backlog 2
trace:winsock:DllMain 0x7dfa0000 0x2 (nil)
trace:winsock:WS_accept socket 00bc

when starting up the app with debug socket checked.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the wine-bugs mailing list