Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 13 Jan 2005 17:42:04 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: stderr ?= stdout
Message-ID: <20050113164204.GV23702@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <u1xcq2ym9 DOT fsf AT gnu DOT org> <20050113101341 DOT GT23702 AT cygbert DOT vinschen DOT de> <u3bx51iqs DOT fsf AT gnu DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <u3bx51iqs.fsf@gnu.org>
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 AT cygwin DOT 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/