From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] PR python/12149 (stderr output directed to stdout)
Date: Fri, 18 Mar 2011 10:23:00 -0000 [thread overview]
Message-ID: <m3d3loq3lq.fsf@redhat.com> (raw)
In-Reply-To: <83wrjxsgn0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Mar 2011 21:15:15 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> +@item STDERR
>> +@value{GDBN}'s error stream.
>
> "standard error", I think.
Ok.
>> +@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?
Ok.
>> +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?
New doc patch inline. What do you think?
Cheers
Phil
--
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.813
diff -u -r1.813 gdb.texinfo
--- doc/gdb.texinfo 17 Mar 2011 09:36:16 -0000 1.813
+++ doc/gdb.texinfo 18 Mar 2011 07:37:17 -0000
@@ -20877,18 +20877,64 @@
@end smallexample
@end defun
-@findex gdb.write
-@defun write string
-Print a string to @value{GDBN}'s paginated standard output stream.
+@findex gdb.write
+@defun write string @r{[}stream{]}
+Print a string to @value{GDBN}'s paginated output stream. The
+optional @var{stream} determines the stream to print to. The default
+stream is @value{GDBN}'s standard output stream. Possible stream
+values are:
+
+@table @code
+@findex STDOUT
+@findex gdb.STDOUT
+@item STDOUT
+@value{GDBN}'s standard output stream.
+
+@findex STDERR
+@findex gdb.STDERR
+@item STDERR
+@value{GDBN}'s standard error stream.
+
+@findex STDLOG
+@findex gdb.STDLOG
+@item STDLOG
+@value{GDBN}'s log stream (@pxref{Logging Output}).
+@end table
+
Writing to @code{sys.stdout} or @code{sys.stderr} will automatically
-call this function.
+call this function and will automatically direct the output to the
+relevant stream.
@end defun
@findex gdb.flush
@defun flush
-Flush @value{GDBN}'s paginated standard output stream. Flushing
-@code{sys.stdout} or @code{sys.stderr} will automatically call this
-function.
+Flush the buffer of a @value{GDBN} paginated stream so that the
+contents are displayed immediately. @value{GDBN} will flush the
+contents of a stream automatically when it encounters a newline in the
+buffer. The optional @var{stream} determines the stream to flush. The
+default stream is @value{GDBN}'s standard output stream. Possible
+stream values are:
+
+@table @code
+@findex STDOUT
+@findex gdb.STDOUT
+@item STDOUT
+@value{GDBN}'s standard output stream.
+
+@findex STDERR
+@findex gdb.STDERR
+@item STDERR
+@value{GDBN}'s standard error stream.
+
+@findex STDLOG
+@findex gdb.STDLOG
+@item STDLOG
+@value{GDBN}'s log stream (@pxref{Logging Output}).
+
+@end table
+
+Flushing @code{sys.stdout} or @code{sys.stderr} will automatically
+call this function for the relevant stream.
@end defun
@findex gdb.target_charset
next prev parent reply other threads:[~2011-03-18 7:40 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 [this message]
2011-03-18 12:11 ` Eli Zaretskii
2011-03-17 19:54 ` Tom Tromey
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=m3d3loq3lq.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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