From: Tom Tromey <tromey@redhat.com>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] PR python/12149 (stderr output directed to stdout)
Date: Thu, 17 Mar 2011 19:54:00 -0000 [thread overview]
Message-ID: <m3sjulzg00.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m31v25slqi.fsf@redhat.com> (Phil Muldoon's message of "Thu, 17 Mar 2011 17:25:09 +0000")
>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
Phil> This patch addresses the bug in python/12149 where output from the Python
Phil> sys.stderr was being directed to stdout within GDB. In this patch I
Phil> have updated gdb.write and flush to take a stream argument, and also
Phil> created a new class to deal with error output.
Phil> OK?
The code bits look good, thanks.
Tom
prev parent reply other threads:[~2011-03-17 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 19:29 Phil Muldoon
2011-03-17 19:47 ` Eli Zaretskii
2011-03-18 10:23 ` Phil Muldoon
2011-03-18 12:11 ` Eli Zaretskii
2011-03-17 19:54 ` Tom Tromey [this message]
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=m3sjulzg00.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@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