From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: separating gdb & inferior output
Date: Wed, 25 Aug 2004 04:07:00 -0000 [thread overview]
Message-ID: <01c48a58$Blat.v2.2.2$5abe69c0@zahav.net.il> (raw)
In-Reply-To: <20040824190912.GB17542@white> (message from Bob Rossi on Tue, 24 Aug 2004 15:09:12 -0400)
> Date: Tue, 24 Aug 2004 15:09:12 -0400
> From: Bob Rossi <bob@brasko.net>
> Cc: gdb@sources.redhat.com
>
> > Perhaps you could state what are the problems with `tty'?
>
> O, you need to actually get a new tty.
Sorry, I still don't get it: I know what the `tty' command does, but I
don't understand what is its problem on non-Unix platforms. I don't
see anything dubious in the code that implements the command.
> Windows doesn't have the concept of a tty.
Of course, it does.
> File descriptor redirection is fine.
And that's exactly what win32-nat.c does, please take a look.
> Maybe we could have something like
>
> gdb --i=mi --out_fd=n
> where n is the descriptor you plan on reading from GDB.
How is this different from what GDB already does?
> What does it mean to open a 'tty' on a windows platform, or some other
> non-unix platform?
Again, see win32-nat.c (search for "inferior_io_terminal").
I'm afraid I'm missing something.
next prev parent reply other threads:[~2004-08-25 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 16:12 Bob Rossi
2004-08-24 19:05 ` Eli Zaretskii
2004-08-24 19:09 ` Bob Rossi
2004-08-25 4:07 ` Eli Zaretskii [this message]
2004-08-25 11:41 ` Bob Rossi
2004-08-25 18:34 ` Eli Zaretskii
2004-08-30 19:23 ` 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='01c48a58$Blat.v2.2.2$5abe69c0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.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