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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 30 Jan 2002 20:49:43 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin port of rsync -- patch for Win2k (rsync 2.5.1) Message-ID: <20020131014943.GE22296@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3C581EC5 DOT 20100 AT rochester DOT rr DOT com> <3C587F40 DOT FB1EED18 AT lapo DOT it> <20020131014357 DOT GC22296 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020131014357.GC22296@redhat.com> User-Agent: Mutt/1.3.23.1i On Wed, Jan 30, 2002 at 08:43:57PM -0500, Christopher Faylor wrote: >On Thu, Jan 31, 2002 at 12:18:24AM +0100, Lapo Luchini wrote: >I am not saying that there can't be a problem but the analysis that the ^ some other kind of >parent process is closing something in the child really can't be >correct. > >As always, I'd appreciate debugging of this situation. It's a given >that one doesn't implicitly have knowledge. You have to gain knowledge >by looking at the code and running the debugger. The techniques in >the file how-to-debug-cygwin.txt should provide you with ways to get >started. -- 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/