From: Vladimir Prus <vladimir@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: "target remote | " stderr -- try2
Date: Mon, 26 Mar 2007 05:32:00 -0000 [thread overview]
Message-ID: <200703260931.58939.vladimir@codesourcery.com> (raw)
In-Reply-To: <ups6x9il1.fsf@gnu.org>
On Monday 26 March 2007 00:25, Eli Zaretskii wrote:
> > From: Vladimir Prus <vladimir@codesourcery.com>
> > Date: Sun, 25 Mar 2007 16:35:13 +0300
> >
> > This is a revision of my earlier patch to make
> > stderr output from program run with
> >
> > target remote | some_program
> >
> > to be routed through gdb_stderr, so that MI
> > frontend sees that output.
>
> Should this be reflected in the manual?
I'm not sure. The fact that some_program's stderr is
not routed via MI output streams seems like an
outright bug to me, so fixing it does not require
documentation.
- Volodya
next prev parent reply other threads:[~2007-03-26 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 13:35 Vladimir Prus
2007-03-25 20:25 ` Eli Zaretskii
2007-03-26 5:32 ` Vladimir Prus [this message]
2007-03-29 18:06 ` Daniel Jacobowitz
2007-04-06 6:07 ` Vladimir Prus
2007-04-06 8:24 ` Mark Kettenis
2007-04-07 17:36 ` 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=200703260931.58939.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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