Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Johnny B. Goode" To: "'cygwin AT cygwin DOT com'" X-Originating-Email: [menotreadthis AT hotmail DOT com] X-Sender: menotreadthis AT hotmail DOT com Message-ID: <60E7170809CCCCCCCCCCC66237ECDE743B1B6C@hotmail.com> References: <20050610215546 DOT GA25218 AT calimero DOT vinschen DOT de> Subject: Re: Re: Error piping data through a cygwin command using rsh (write system call fail) Date: Fri, 10 Jun 2005 11:06:20 +0200 In-Reply-To: <20050610215546.GA25218@calimero.vinschen.de> On Fri, 10 Jun 2005 23:55:46, Corinna Vinschen wrote: > Thanks for the testcase. It took some time to reproduce it (actually > the error occured with quite different result on my machine) and to track > it down, but I think I have found the culprit, an uninitialized variable > in the socket sendto/sendmsg code. After having initialized it to 0, I'm > now unable to get your example to fail. > Or better: http://cygwin.com/acronyms/#WJFFM :-) > > Could you please try the next snapshot from http://cygwin.com/snapshots/ > to see if it solves the problem for you? Hi Corinna. I've just tried out the indicated snapshot of cygwin1.dll and it seems to solve the problem! I haven't been able to reproduce the error with the new snapshot and it was 100% persistent before. Case closed from my point of view :-) Thanks for quick assistance! Best regards, Soeren Hansen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/