Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Markus Hoenicka" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14900.63927.152000.146634@gargle.gargle.HOWL> Date: Mon, 11 Dec 2000 15:58:47 +0000 (CT0) To: Corinna Vinschen Subject: Re: socket read()/write() problem in 1.1.6 [solved] In-Reply-To: <00120813285702.12851@cygbert> References: <1529f1887b DOT 1887b1529f AT uth DOT tmc DOT edu> <00120813285702 DOT 12851 AT cygbert> X-Mailer: VM 6.75 under Emacs 20.6.1 Finally it turns out that my problem was indeed a timing problem - not the read()/write() timing problem that Corinna suspected but a timing problem when closing the socket from the server side. I was not aware that my server relied on a certain time passing between the last write() on the server side and the closing of the socket as it was obscured by lots of cleanup code in my original program. This got clearer and clearer the simpler my testcases got. The newer Cygwin versions apparently speed up this cleanup or the closing of the socket and thus expose the flawed design of my server. Of course it is easy to work around this once you know. I'm sorry for the noise that I created, but putting together the testcases and Corinna's input finally helped me to see the problem. regards, Markus -- Markus Hoenicka, PhD UT Houston Medical School Dept. of Integrative Biology and Pharmacology 6431 Fannin MSB4.114 Houston, TX 77030 (713) 500-6313, -7477 (713) 500-7444 (fax) Markus DOT Hoenicka AT uth DOT tmc DOT edu http://ourworld.compuserve.com/homepages/hoenicka_markus/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com