This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[committed] Fix gdb.texinfo for old makeinfo
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: gdb-patches at sourceware dot org
- Cc: nd at arm dot com, John Baldwin <jhb at freebsd dot org>, Eli Zaretskii <eliz at gnu dot org>
- Date: Thu, 11 Jan 2018 12:35:33 +0000
- Subject: [committed] Fix gdb.texinfo for old makeinfo
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Szabolcs dot Nagy at arm dot com;
- Nodisclaimer: True
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
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.
(committed as obvious)
gdb/doc/ChangeLog:
2018-01-11 Szabolcs Nagy <szabolcs.nagy@arm.com>
* gdb.texinfo (pwd): Fix whitespace.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 096c82cc82..dba2fa766a 100644
--- 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.