This is the mail archive of the
mailing list for the Cygwin project.
Re: stderr ?= stdout
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
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:firstname.lastname@example.org
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html