gdb/doc: use 'standard error stream' instead of 'stderr' in some places
authorAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 29 Sep 2021 08:25:03 +0000 (09:25 +0100)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 29 Sep 2021 08:25:03 +0000 (09:25 +0100)
commit4180173142185f0967dfefb131e4843a17779c86
treeb87156a9ade25d7a48a5e78ab10c32a8fa82acc6
parent80656a8e4b32353025f7f4cb1279168f082fbf7b
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.
gdb/doc/gdb.texinfo