From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: "target remote | " stderr
Date: Fri, 26 Jan 2007 14:00:00 -0000 [thread overview]
Message-ID: <20070126140028.GA29456@nevyn.them.org> (raw)
In-Reply-To: <200701261653.53834.vladimir@codesourcery.com>
On Fri, Jan 26, 2007 at 04:53:53PM +0300, Vladimir Prus wrote:
>
> At the moment, when handling
>
> target remote | whatever
>
> gdb does not do anything with 'whatever''s stderr. This is not good,
> because when using MI, frontend might not even look at stderr at all,
> so messages from 'whatever' get lost.
>
> This patch fixes that. The fix is only for Linux, I plan to do the
> same with mingw support, but only if this patch is considered OK.
>
> - Volodya
>
> Pass stderr of program run with "target remote |"
> via gdb_stderr.
> * serial.c (serial_open): Set error_fd to -1.
> * serial.h (struct serial): New field error_fd.
> * ser-pipe.c (pipe_open): Create another pair
> of sockets. Pass stderr to gdb.
> * ser-base.c (generic_readchar): Check if there's
> anything in stderr channel and route that to gdb_stderr.
The patch seems OK to me; though I would like to be sure we can
implement this for MinGW before we get too used to the idea.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-26 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 13:54 Vladimir Prus
2007-01-26 14:00 ` Daniel Jacobowitz [this message]
2007-01-31 14:35 ` Vladimir Prus
2007-01-31 14:41 ` Daniel Jacobowitz
2007-02-11 16:56 ` Vladimir Prus
2007-02-11 18:10 ` Mark Kettenis
2007-02-17 7:50 ` Vladimir Prus
2007-02-11 20:24 ` Eli Zaretskii
2007-02-17 7:35 ` Vladimir Prus
2007-02-17 10:56 ` Eli Zaretskii
2007-02-17 14:31 ` Vladimir Prus
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=20070126140028.GA29456@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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