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 11:13:41 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: stderr ?= stdout
Message-ID:	<20050113101341.GT23702@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>
Mime-Version:	1.0
In-Reply-To:	<u1xcq2ym9.fsf@gnu.org>
User-Agent:	Mutt/1.4.2i

On Jan 12 15:14, Sam Steingold wrote:
> alas, the current cygwin reports different inodes for stdout and stderr:
>   -437397064 and 593767114

That looks suspicious.  Are you aware that ino_t is a 64 bit int?

> so, what is the right way to check that two FDs refer to the
> same device?

You didn't tell which device stdout and stderr are connected to.
Are you running this in a local console?


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/

- Raw text -