Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 13 Jan 2005 17:42:04 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: stderr ?= stdout Message-ID: <20050113164204.GV23702@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20050113101341.GT23702@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jan 13 09:55, Sam Steingold wrote: > when running under pure w2k cmd, or under gdb started from bash, > or under gdb started from cmd, I get identical numbers: > > stderr: 327681 2f61f5afe5edd9b8 8630 1 13044 10513 327681 0 > stdout: 327681 2f61f5afe5edd9b8 8630 1 13044 10513 327681 0 > > (i.e., it appears that _stdout_ inode under bash is bad.) It's not only bash. I see the same when running in another Cygwin shell. It seems to depend on the way the console handler is propagated to the child process so that the information needed to create the inode number is missing afterwards. I'm pretty busy right now but a patch should follow soon. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/