From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: [mingw32] stdin redirection
Date: Thu, 12 Apr 2007 19:33:00 -0000 [thread overview]
Message-ID: <ups69jsl7.fsf@gnu.org> (raw)
In-Reply-To: <20070412164744.GL3886@adacore.com> (message from Joel Brobecker on Thu, 12 Apr 2007 18:47:44 +0200)
> Date: Thu, 12 Apr 2007 18:47:44 +0200
> From: Joel Brobecker <brobecker@adacore.com>
>
> > > If we could find a way to replace the current implementation of
> > > fd_is_pipe into something that avoids using any of the pipe functions,
> > > then that would probably solve our problem. Unfortunately, despite
> > > our intensive search of MSDN, nothing turned up.
> >
> > To the best of my knowledge there is no way.
>
> That's what we though too :-(.
Can't we maintain a list of all file descriptors used by GDB, where
those which are open on a pipe are marked as such? Then we'd _know_
what API with each fd to use without relying on dysfunctional tests.
next prev parent reply other threads:[~2007-04-12 19:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 13:42 Jerome Guitton
2007-04-11 14:45 ` Daniel Jacobowitz
2007-04-11 14:51 ` Jerome Guitton
2007-04-11 15:12 ` Daniel Jacobowitz
2007-04-12 14:56 ` Joel Brobecker
2007-04-12 15:01 ` Dave Korn
2007-04-12 15:04 ` Dave Korn
[not found] ` <20070412155422.GI3886@adacore.com>
2007-04-12 15:58 ` Dave Korn
2007-04-12 16:06 ` Joel Brobecker
2007-04-12 16:09 ` Dave Korn
2007-04-12 15:12 ` Daniel Jacobowitz
2007-04-12 15:51 ` Joel Brobecker
2007-04-12 16:02 ` Daniel Jacobowitz
2007-04-12 16:04 ` Daniel Jacobowitz
2007-04-12 16:29 ` Joel Brobecker
2007-04-12 18:23 ` Daniel Jacobowitz
2007-04-12 18:56 ` Daniel Jacobowitz
2007-04-13 9:07 ` Joel Brobecker
2007-04-12 16:46 ` Joel Brobecker
2007-04-12 17:25 ` Dave Korn
2007-04-13 11:47 ` Jerome Guitton
2007-04-12 19:33 ` Eli Zaretskii [this message]
2007-04-12 19:37 ` Mark Kettenis
2007-04-12 19:51 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ups69jsl7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox