[binutils-gdb] gdb/doc: use 'standard error stream' instead of 'stderr' in some places

[binutils-gdb] gdb/doc: use 'standard error stream' instead of 'stderr' in some places

[Andrew Burgess]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4180173142185f0967dfefb131e4843a17779c86

commit 4180173142185f0967dfefb131e4843a17779c86
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date:   Wed Sep 29 09:25:03 2021 +0100

    gdb/doc: use 'standard error stream' instead of 'stderr' in some places
    
    With this commit:
    
      commit 91f2597bd24d171c1337a4629f8237aa47c59082
      Date:   Thu Aug 12 18:24:59 2021 +0100
    
          gdb: print backtrace for internal error/warning
    
    I included some references to 'stderr', which, it was pointed out,
    would be better written as 'standard error stream'.  See:
    
      https://sourceware.org/pipermail/gdb-patches/2021-September/182225.html
    
    This commit replaces the two instances of 'stderr' that I introduced.

Diff:
---
 gdb/doc/gdb.texinfo | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index d4e4174be5d..c156a1d6739 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -39266,9 +39266,9 @@ disabled.
 @itemx maint set internal-warning backtrace @r{[}on|off@r{]}
 @itemx maint show internal-warning backtrace
 When @value{GDBN} reports an internal problem (error or warning) it is
-possible to have a backtrace of @value{GDBN} printed to stderr.  This
-is @samp{on} by default for @code{internal-error} and @samp{off} by
-default for @code{internal-warning}.
+possible to have a backtrace of @value{GDBN} printed to the standard
+error stream.  This is @samp{on} by default for @code{internal-error}
+and @samp{off} by default for @code{internal-warning}.
 
 @kindex maint packet
 @item maint packet @var{text}
@@ -39768,9 +39768,9 @@ the settings infrastructure.
 @itemx maint show backtrace-on-fatal-signal
 When this setting is @code{on}, if @value{GDBN} itself terminates with
 a fatal signal (e.g.@: SIGSEGV), then a limited backtrace will be
-printed to stderr.  This backtrace can be used to help diagnose
-crashes within @value{GDBN} in situations where a user is unable to
-share a corefile with the @value{GDBN} developers.
+printed to the standard error stream.  This backtrace can be used to
+help diagnose crashes within @value{GDBN} in situations where a user
+is unable to share a corefile with the @value{GDBN} developers.
 
 If the functionality to provide this backtrace is not available for
 the platform on which GDB is running then this feature will be