This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] PR python/12149 (stderr output directed to stdout)
- From: Eli Zaretskii <eliz at gnu dot org>
- To: pmuldoon at redhat dot com
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 17 Mar 2011 21:15:15 +0200
- Subject: Re: [patch] PR python/12149 (stderr output directed to stdout)
- References: <m31v25slqi.fsf@redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Phil Muldoon <pmuldoon@redhat.com>
> Date: Thu, 17 Mar 2011 17:25:09 +0000
>
> This patch addresses the bug in python/12149 where output from the Python
> sys.stderr was being directed to stdout within GDB. In this patch I
> have updated gdb.write and flush to take a stream argument, and also
> created a new class to deal with error output.
Thanks.
> +@item STDERR
> +@value{GDBN}'s error stream.
"standard error", I think.
> +@item STDLOG
> +@value{GDBN}'s log stream.
This may need a word or two of explanation, because it's not a
standard stream like stdout and stderr. It goes to where "set
logging" directs it, right? If so, how about a cross-reference to
where the logging facility is described?
> +Flush a @value{GDBN} paginated stream. The optional @var{stream}
> +determines the stream to flush. The default stream is @value{GDBN}'s
> +standard output stream. Possible stream values are:
Are you sure the reader will know the effect of "flushing" a strem
without any explanations?