🚀 go-pugleaf

"jer" <jer_bred_guy@yahoo.com> wrote in message
news:1159392295.406227.295400@e3g2000cwe.googlegroups.com...

> Before the sendto function I always use select to determine if the socket
is writable.

That is generally not a good idea.  You should just call sendto() by itself,
and let it report an error if it cannot send.

> However, intermittently, the select statement times out (I set it to
> a 3 sec timeout).  When this happens I skip the sendto function and try
> the select again. At this point, select returns SOCKET_ERROR and
> I get a 10022 error (invalid argument) when I call WSAGetLastError().

From the select() documentation:

    WSAEINVAL
    The timeout value is not valid, or all three descriptor parameters were
NULL.

Please show your actual socket code.

> From this point on, I use select to check if the socket is writable and
> each time I get SOCKET_ERROR with 10022.

My guess would be that your socket is no longer valid.

> After this happens, I have tried to diagnose what is going on in
> the PC. I have tried pinging the other computer on the network,
> and I always get "destination unreachable".

You lost your network connection.  Try rebooting the machine, and
double-check the network wires.

> Then I tried pinging localhost and I get destination unreachable.

You probably blew up the TCP/IP stack altogether.  Pinging the localhost
should never fail when TCP/IP is working properly.

> Why would select suddenly timeout after working properly for 10
> minutes?

Hard to say without seeing your actual code.

> Why would I get an invalid argument error after successfully
> using the same select code many times before?

Because the socket is no longer valid.

> What could I be doing to break ping?

Hard to say without seeing your actual code.

> Why can't I ping localhost?

Because TCP/IP is not working properly anymore.


Gambit