From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,be3d89c2ad66a506 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.glorb.com!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-rtr.nyroc.rr.com!news-out.nyroc.rr.com!twister.nyroc.rr.com.POSTED!53ab2750!not-for-mail From: "REH" Newsgroups: comp.lang.ada References: <1131117934.372137.244900@g44g2000cwa.googlegroups.com> Subject: Re: Advice on abort X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2670 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Message-ID: Date: Sun, 06 Nov 2005 20:41:17 GMT NNTP-Posting-Host: 69.205.134.80 X-Complaints-To: abuse@rr.com X-Trace: twister.nyroc.rr.com 1131309677 69.205.134.80 (Sun, 06 Nov 2005 15:41:17 EST) NNTP-Posting-Date: Sun, 06 Nov 2005 15:41:17 EST Organization: Road Runner Xref: g2news1.google.com comp.lang.ada:6257 Date: 2005-11-06T20:41:17+00:00 List-Id: "Simon Wright" wrote in message news:m27jbla69k.fsf@grendel.local... > "REH" writes: > >> "Simon Wright" wrote in message >> news:m2br0y9g9w.fsf@grendel.local... >>> "REH" 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. > Ah, I see. I did misunderstand you. Sorry.