From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: separating gdb & inferior output
Date: Tue, 24 Aug 2004 19:09:00 -0000 [thread overview]
Message-ID: <20040824190912.GB17542@white> (raw)
In-Reply-To: <01c48a0c$Blat.v2.2.2$ba4a7920@zahav.net.il>
On Tue, Aug 24, 2004 at 10:00:11PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 24 Aug 2004 12:11:47 -0400
> > From: Bob Rossi <bob@brasko.net>
> >
> > I have the feeling the tty command does not port properly everywhere
> > that GDB does (mingw, cygwin). I've personally had problems with it on
> > some version of Windows with cygwin. Besides, figuring out how to open a
> > tty on different machines is a real pain.
> >
> > Is there a better, more portable way, to accomplish the same task?
>
> What can be more portable than file descriptor redirection? Even
> MS-DOS supports it.
>
> > I was thinking of having GDB output it's output to a UNIX or TCP/IP
> > port. How about a FIFO(portable?)? Any other ideas?
>
> Both are less portable than redirection, IMHO. FIFOs are
> Unix-specific, and ports will not work on a system without a network
> interface.
>
> Perhaps you could state what are the problems with `tty'?
O, you need to actually get a new tty. Windows doesn't have the concept
of a tty. File descriptor redirection is fine. Maybe we could have
something like
gdb --i=mi --out_fd=n
where n is the descriptor you plan on reading from GDB.
What does it mean to open a 'tty' on a windows platform, or some other
non-unix platform?
Thanks,
Bob Rossi
next prev parent reply other threads:[~2004-08-24 19:09 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 [this message]
2004-08-25 4:07 ` Eli Zaretskii
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=20040824190912.GB17542@white \
--to=bob@brasko.net \
--cc=eliz@gnu.org \
--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