X-Spam-Check-By: sourceware.org Date: Thu, 17 Aug 2006 17:26:16 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: Snapshot uploaded, please try In-Reply-To: <20060810212525.GA11554@trixie.casa.cgf.cx> Message-ID: References: <20060810142651 DOT GA32470 AT trixie DOT casa DOT cgf DOT cx> <82k65gp9v0 DOT fsf AT vzell-de DOT de DOT oracle DOT com> <20060810212525 DOT GA11554 AT trixie DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Thu, 10 Aug 2006, Christopher Faylor wrote: > On Thu, Aug 10, 2006 at 11:19:15PM +0200, Dr. Volker Zell wrote: > >Starting xterm from an rxvt window gives: > >In the Xterm window > > 587214 [main] xterm 296 modify_handle: virtual void fhandler_pipe::set_close_on_exec(bool):175 handle guard<0x680> not found > > That one *could* be responsible. I was suspecting something in the pipe > code since it has often been the cause of handle closing confusion. Just in case anyone wants another simple test case: $ cat makefile all: echo hi $ make echo hi 7486 [main] make 2648 modify_handle: virtual void fhandler_pipe::set_close_on_exec(bool):175 handle guard<0x734> not found hi $ uname -a CYGWIN_NT-5.1 PC1163-8460-XP 1.7.0(0.160/4/2) 2006-08-17 08:07 i686 unknown unknown Cygwin I'm looking at it as time permits, but I'm not optimistic I will decipher enough to fix it :-(. Note that running it under strace causes a hang here: $ strace -o junk make echo hi with make eating all the CPU. -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... . -- 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/