Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [pushed] Remove extra space after @pxref in gdb.texinfo
Date: Wed, 27 Jan 2021 06:57:33 -0700	[thread overview]
Message-ID: <20210127135733.2476752-1-tromey@adacore.com> (raw)

Internally at AdaCore, documentation is still built with Texinfo 4.13.
This version gave an error when building gdb.texinfo:

../../../binutils-gdb/gdb/doc/gdb.texinfo:27672: @pxref expected braces.
../../../binutils-gdb/gdb/doc/gdb.texinfo:27672: ` {dotdebug_gdb_scripts section,,The @cod...' is too long for expansion; not expanded.

... followed by many more spurious errors that were caused by this
one.

This patch fix the problem by removing the extra space.

I don't know whether it's advisable to try to support this ancient
version of Texinfo (released in 2008 apparently); but in this
particular case the fix is trivial, so I'm checking it in.

gdb/doc/ChangeLog
2021-01-27  Tom Tromey  <tromey@adacore.com>

	* gdb.texinfo (Auto-loading extensions): Remove extraneous space.
---
 gdb/doc/ChangeLog   | 4 ++++
 gdb/doc/gdb.texinfo | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index e43819f0f70..84243a72eaf 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -27669,7 +27669,7 @@ extensions when a new object file is read (for example, due to the
 library): @file{@var{objfile}-gdb.@var{ext}} (@pxref{objfile-gdbdotext
 file,,The @file{@var{objfile}-gdb.@var{ext}} file}) and the
 @code{.debug_gdb_scripts} section of modern file formats like ELF
-(@pxref {dotdebug_gdb_scripts section,,The @code{.debug_gdb_scripts}
+(@pxref{dotdebug_gdb_scripts section,,The @code{.debug_gdb_scripts}
 section}).  For a discussion of the differences between these two
 approaches see @ref{Which flavor to choose?}.
 
-- 
2.26.2


             reply	other threads:[~2021-01-27 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 13:57 Tom Tromey [this message]
2021-01-27 14:06 ` Andrew Burgess

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=20210127135733.2476752-1-tromey@adacore.com \
    --to=tromey@adacore.com \
    --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