Fix gdb.texinfo for old makeinfo

With old makeinfo (version 4.13) the changes introduced in

commit 2d97a5d9d33aea87c3bd02fd1fa417f5d4e1fa05
Author:     John Baldwin <jhb@FreeBSD.org>

    Document support for 'info proc' on FreeBSD.

fail to build.

gdb/doc/ChangeLog:

	* gdb.texinfo (pwd): Fix whitespace.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 940f1d404c7d1cc73489d5ab825d9e5f780893c0..76ce904635830f3ecfde2837c4c9108402daceb3 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2018-01-11  Szabolcs Nagy  <szabolcs.nagy@arm.com>
+
+       * gdb.texinfo (pwd): Fix whitespace.
+
 2018-01-09  John Baldwin  <jhb@FreeBSD.org>
 
        * gdb.texinfo (pwd): Update cross-reference for Process Information

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 096c82cc8214ce741af3e0f22d6a8f4aac085a3e..dba2fa766ab2162f593eea9ea6ef7559f0e7bd3d 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -2524,7 +2524,7 @@ Print the @value{GDBN} working directory.
 It is generally impossible to find the current working directory of
 the process being debugged (since a program can change its directory
 during its run).  If you work on a system where @value{GDBN} supports
-the @code {info proc} command (@pxref{Process Information}), you can
+the @code{info proc} command (@pxref{Process Information}), you can
 use the @code{info proc} command to find out the
 current working directory of the debuggee.