From: Sam S. <sd...@gn...> - 2008-12-22 19:18:26
|
Don Cohen wrote: > I've recently noticed that socket-status can signal an error. > Actually, this has been happening for a long time, but I only > recently got around to debugging it. I don't see anything about > this in the doc, so this seems like either a problem in the code > or a problem in the doc. If errors are (supposed to be) possible > I'd like the doc to describe which errors and under which > circumstances. I don't think socket-status should signal errors. > *** - UNIX error 104 (ECONNRESET): Connection reset by peer > The following restarts are available: > ABORT :R1 Abort main loop > Break 1 HTTP[19]> where > <1/101> #<SYSTEM-FUNCTION SOCKET:SOCKET-STATUS> > [98] EVAL frame for form (SOCKET:SOCKET-STATUS SSS::*SOCKET-STATUS-ARG* TIME) > > (BTW, what do the <1/101> and [98] mean here?) see print_back_trace & print_stackitem in debug.d > In this case, the timeout argument is non-zero. > I've now put an ignore-errors around this call, which I think will fix > this case, but I also have a number of calls to socket-status with > timeout zero - can those ever cause errors? if the socket is dead, many bad things can happen. if you have a reproducible case, I am interested. |