Re: Advice on abort

[Simon Wright <simon@pushface.org>]

"REH" <me@you.com> writes:

> "Simon Wright" <simon@pushface.org> wrote in message 
> news:m2br0y9g9w.fsf@grendel.local...
>> "REH" <me@you.com> writes:
>>
>>> That's fine.  We are VxWorks too.  Besides, a return of 0 on a read
>>> is not considered "successful" with sockets.  It means the socket
>>> has been closed.  You got an exception on the next read, because you
>>> were trying to read from a closed socket.
>>
>> Yes -- but the bug didn't show on Windows because of the different OS
>> behaviour.
>
> I don't understand.  What bug?  A return of 0 is not a bug.  I don't think 
> you've encountered different OS behavior.  winsock will also return 0 from 
> read when a socket closes.  If I understand you correctly, you've 
> encountered a particular behavior with GNAT on Windows, not Windows itself. 
> Or I may have completely misunderstood what you were saying.

The bug in our software where we didn't check the length returned.

Mind, I too think that we should have seen a return of 0 under
Windows, and I am completely convinced (but the evidence isn't on this
machine) that we didn't. We should see an End_Error from String'Input
but instead we se a Socket_Error with 'connection reset by peer'.

You could be right that it's a GNAT thing, but the GNAT code looks
identical in this area.