From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: brobecker@adacore.com, uweigand@de.ibm.com, gdb-patches@sourceware.org
Subject: Re: Support of gdb for Windows 64 native systems
Date: Thu, 18 Oct 2007 04:16:00 -0000 [thread overview]
Message-ID: <uhckphxri.fsf@gnu.org> (raw)
In-Reply-To: <471685D3.7060402@portugalmail.pt> (message from Pedro Alves on Wed, 17 Oct 2007 22:59:47 +0100)
> Date: Wed, 17 Oct 2007 22:59:47 +0100
> From: Pedro Alves <pedro_alves@portugalmail.pt>
> CC: Ulrich Weigand <uweigand@de.ibm.com>, Eli Zaretskii <eliz@gnu.org>,
> gdb-patches@sourceware.org
>
> There's these 'HANDLE hStdInput, hStdOutput, hStdError' in
> STARTUPINFO which may be passed into the CreateProcess call to
> redirect io. Yet another way is to use GetStdHandle/SetStdHandle
> much like one uses dup2 on unix. In both these alternatives
> we'll have to do args processing (<,>, etc) ourselves.
I agree that we should do it by redirecting handles directly, not
through the shell.
> But, is this considered a basic feature? I seldom use it myself.
> I don't think it is a show stopper.
I don't think it's a show-stopper, just a (temporary) lack of feature.
For example, the DJGPP port was part of GDB for years before
redirection support was added.
next prev parent reply other threads:[~2007-10-18 4:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uprzkkrf7.fsf@gnu.org>
[not found] ` <20071012222842.GD21800@adacore.com>
[not found] ` <20071013024116.GB29152@adacore.com>
[not found] ` <uk5prl27s.fsf@gnu.org>
[not found] ` <20071013154715.GE29152@adacore.com>
[not found] ` <4711021C.8010805@portugalmail.pt>
[not found] ` <20071013205105.GA13789@adacore.com>
[not found] ` <47114BB7.1000501@portugalmail.pt>
[not found] ` <20071014051622.GC13789@adacore.com>
[not found] ` <471200C5.6050609@portugalmail.pt>
2007-10-14 18:03 ` Christopher Faylor
2007-10-14 19:55 ` Pedro Alves
2007-10-14 22:22 ` Christopher Faylor
2007-10-14 23:14 ` Daniel Jacobowitz
2007-10-15 18:54 ` Christopher Faylor
2007-10-15 19:19 ` Daniel Jacobowitz
2007-10-16 0:18 ` Pedro Alves
2007-10-16 4:21 ` Eli Zaretskii
2007-10-16 6:40 ` Christopher Faylor
2007-10-16 11:57 ` Pedro Alves
2007-10-16 12:41 ` Eli Zaretskii
2007-10-16 14:35 ` Christopher Faylor
2007-10-16 14:41 ` Pedro Alves
2007-10-16 15:56 ` Daniel Jacobowitz
2007-10-16 16:13 ` Christopher Faylor
2007-10-16 16:16 ` Eli Zaretskii
2007-10-16 18:23 ` Joel Brobecker
2007-10-16 18:57 ` Ulrich Weigand
2007-10-17 19:47 ` Pedro Alves
2007-10-17 22:00 ` Joel Brobecker
2007-10-18 4:06 ` Pedro Alves
2007-10-18 4:16 ` Eli Zaretskii [this message]
2007-10-18 10:07 ` Joel Brobecker
2007-10-18 20:20 ` Eli Zaretskii
2007-10-19 11:48 ` Joel Brobecker
2007-10-19 12:09 ` Daniel Jacobowitz
2007-10-19 12:27 ` Eli Zaretskii
2007-10-16 20:29 ` Pedro Alves
2007-10-14 23:29 ` Pedro Alves
2007-10-15 18:45 ` Christopher Faylor
2007-10-15 23:32 ` Pedro Alves
2007-10-14 21:16 ` Joel Brobecker
2007-10-14 22:22 ` Christopher Faylor
2007-10-15 8:58 ` Pedro Alves
2007-10-15 18:39 ` Christopher Faylor
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=uhckphxri.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
--cc=uweigand@de.ibm.com \
/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