From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: gdb-patches@sourceware.org
Cc: nd@arm.com, John Baldwin <jhb@freebsd.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: [committed] Fix gdb.texinfo for old makeinfo
Date: Thu, 11 Jan 2018 12:35:00 -0000 [thread overview]
Message-ID: <5A575A15.10404@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
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.
[-- Attachment #2: gdbinfo.diff --]
[-- Type: text/x-patch, Size: 652 bytes --]
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.
next reply other threads:[~2018-01-11 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 12:35 Szabolcs Nagy [this message]
2018-01-11 16:09 ` Eli Zaretskii
2018-01-11 18:49 ` John Baldwin
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=5A575A15.10404@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=nd@arm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).