Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Originating-IP: [194.224.58.37]
From: "Miguelanxo Otero" <miguelanxotero AT hotmail DOT com>
To: lhall AT rfk DOT com
Cc: cygwin AT cygwin DOT com
Subject: Re: write() on closed socket crashes program instead of reporting error
Date: Wed, 24 Oct 2001 22:06:53 
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F124gVvpQN1RmpS31bT0001b866@hotmail.com>
X-OriginalArrivalTime: 24 Oct 2001 22:06:53.0775 (UTC) FILETIME=[3065BDF0:01C15CD8]

No, I only test it under 1.3.2 but I think that, as my program follows the 
classic way of I/O code, there must be a bug, and I wonder how it could pass 
without notice. Or maybe I have done something wrong...

But, hey! how can you asure a socket will be open when you start write()'ing 
to it?

Or, what about apache? is this bug showing there?


>From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
>To: "Miguelanxo Otero" <miguelanxotero AT hotmail DOT com>, cygwin AT cygwin DOT com
>Subject: Re: write() on closed socket crashes program instead of  reporting 
>error
>Date: Wed, 24 Oct 2001 10:25:50 -0400
>
>At 09:44 AM 10/24/2001, Miguelanxo Otero wrote:
> >Ok, this time i'll try to be very concise.
> >
> >Im porting a linux application (a web server). The web server is able to 
>manage different connections at a time (max 10 connections).
> >
> >The problem is this... Imagine tou are downloading a page & in the middle 
>of the download you kill (or press the stop button in) the web browser 
>(client application). Then, if my web server tries to write() in the 
>(closed | killed) socket, instead of reporting an error, the program 
>crashes.
> >
> >If i run my web server in the bash console of cygwin, it reports an 
>"broken pipe" error after crashing.
> >
> >If I run the web server in a ms-dos console, it dies silently.
> >
> >the code is like this:
> >
> >if ((count=write(client_socket,requested_web_page_buffer,length))==-1) {
> >perror("write");
> >free_stuff_of_this_connection();
> >}
> >
> >In linux, if write fails, perror reports the error and the program frees 
>connection & keeps running ok.
> >
> >In windows (cygwin) if write fails, perror doesn't report anything & 
>program crashes.
> >
> >Im using cygwin1.dll version 1.3.2.
>
>
>Have you tried 1.3.3 or a snapshot?  It would be quite helpful to know
>if you have.  Sorry if I missed part of some previous thread here which
>indicates that you have done this already.
>
>
>
>Larry Hall                              lhall AT rfk DOT com
>RFK Partners, Inc.                      http://www.rfk.com
>118 Washington Street                   (508) 893-9779 - RFK Office
>Holliston, MA 01746                     (508) 893-9889 - FAX
>


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/