Windows: socket send error 10038 in debug.log #2587

issue Diapolo opened this issue on April 28, 2013
  1. Diapolo commented at 2:31 PM on April 28, 2013: none

    Anyone around here that also has this error in his debug.log?

    MSDN is telling this about 10038: WSAENOTSOCK 10038 Socket operation on nonsocket.

    An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

    http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668%28v=vs.85%29.aspx

  2. laanwj commented at 2:59 PM on April 28, 2013: member

    Looks like either a use-after-close or an error value that is not properly checked (and thus used a socket handle). Does it happen predictably? Another possibility is that somehow a non-socket value sneaks into one of the descriptor list of select.

  3. sipa commented at 3:04 PM on April 28, 2013: member

    On IRC @Diapolo mentioned that it was a socket send error, which would mean SocketSendData is called on a CNode without valid hSocket field.

  4. sipa commented at 2:24 PM on April 30, 2013: member

    See #2595.

  5. Diapolo closed this on May 2, 2013

  6. DrahtBot locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-19 12:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me