From: Jim Blandy <jimb@red-bean.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Daniel Jacobowitz <drow@false.org>,
Denis PILAT <denis.pilat@st.com>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Target stderr not displayed thru MI
Date: Fri, 02 Dec 2005 01:26:00 -0000 [thread overview]
Message-ID: <8f2776cb0512011723s4b70d47dr6ffc0e2ff6ecaafb@mail.gmail.com> (raw)
In-Reply-To: <17295.22919.290876.649298@kahikatea.snap.net.nz>
Adding a new MI output stream with its own magic character will break
existing MI clients. I don't think that's worthwhile, especially
given that, when a program is talking to a TTY, you can't distinguish
the two either.
If, at some point in the future, the MI protocol does get extended to
distinguish the two streams, the code will be ready for it, since we
already distinguish gdb_stdtarg and gdb_stdtargerr internally. This
change doesn't make future improvements difficult.
next prev parent reply other threads:[~2005-12-02 1:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 14:15 Nick Roberts
2005-11-30 18:57 ` [PATCH] " Denis PILAT
2005-11-30 19:03 ` Bob Rossi
2005-11-30 19:55 ` Daniel Jacobowitz
[not found] ` <17294.2894.345752.773239@kahikatea.snap.net.nz>
2005-12-01 13:57 ` Denis PILAT
2005-12-01 14:06 ` Bob Rossi
2005-12-01 14:32 ` Daniel Jacobowitz
2005-12-01 16:20 ` Denis PILAT
2005-12-01 22:49 ` Nick Roberts
2005-12-02 1:26 ` Jim Blandy [this message]
2005-12-05 20:50 ` Denis PILAT
2005-12-06 6:09 ` Nick Roberts
2005-12-06 10:49 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2005-11-30 2:47 Denis PILAT
2005-11-30 13:51 ` Jim Blandy
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=8f2776cb0512011723s4b70d47dr6ffc0e2ff6ecaafb@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=denis.pilat@st.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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