[pushed] Fix gdb.texinfo build

Message ID 20190314190942.8203-1-simon.marchi@efficios.com
State New
Headers show
  • [pushed] Fix gdb.texinfo build
Related show

Commit Message

Simon Marchi March 14, 2019, 7:09 p.m.
Commit b4be1b064860 ("Fix MI output for multi-location breakpoints")
broke the build of gdb.texinfo.  The problem is simply the use of "@end
@table", which should be "@end table".

The error was:

    /home/smarchi/src/binutils-gdb/gdb/doc/gdb.texinfo:27870: warning: @table should not appear in @end
    /home/smarchi/src/binutils-gdb/gdb/doc/gdb.texinfo:27870: table requires an argument: the formatter for @item
    /home/smarchi/src/binutils-gdb/gdb/doc/gdb.texinfo:27870: no matching `@end table'
    /home/smarchi/src/binutils-gdb/gdb/doc/gdb.texinfo:27870: bad argument to @end: @table
    /home/smarchi/src/binutils-gdb/gdb/doc/gdb.texinfo:27867: warning: @table has text but no @item
    /home/smarchi/src/binutils-gdb/gdb/doc/gdb.texinfo:27879: @node seen before @end table


	* gdb.texinfo (GDB/MI Development and Front Ends): Fix closing
	of table, "@end @table" -> "@end table".
 gdb/doc/ChangeLog   | 5 +++++
 gdb/doc/gdb.texinfo | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)



diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 1b7dabffa221..6b9911c54365 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@ 
+2019-03-14  Simon Marchi  <simon.marchi@efficios.com>
+	* gdb.texinfo (GDB/MI Development and Front Ends): Fix closing
+	of table, "@end @table" -> "@end table".
 2019-03-14  Tom Tromey  <tromey@adacore.com>
 	* gdb.texinfo (Output Styling): Document "set style source" and
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 431752b4110b..271739b6cdc9 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -27881,7 +27881,7 @@  Use the output for multi-location breakpoints which was introduced by
 MI 3, even when using MI versions 2 or 1.  This command has no
 effect when using MI version 3 or later.
-@end @table
+@end table
 The best way to avoid unexpected changes in MI that might break your front
 end is to make your project known to @value{GDBN} developers and