From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCH] Install and generate docs for gdb-add-index
Date: Fri, 12 Jan 2018 08:34:00 -0000 [thread overview]
Message-ID: <83vag7329f.fsf@gnu.org> (raw)
In-Reply-To: <20180111213530.23774-1-sergiodj@redhat.com> (message from Sergio Durigan Junior on Thu, 11 Jan 2018 16:35:30 -0500)
> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: Tom Tromey <tom@tromey.com>, Eli Zaretskii <eliz@gnu.org>, Sergio Durigan Junior <sergiodj@redhat.com>
> Date: Thu, 11 Jan 2018 16:35:30 -0500
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index dba2fa766a..62fcdd524e 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -19775,6 +19775,14 @@ There are currently some limitation on indices. They only work when
> for DWARF debugging information, not stabs. And, they do not
> currently work for programs using Ada.
>
> +@value{GDBN} comes with a program, @command{gdb-add-index}, which can
> +be used to add the index to a symbol file. It takes the symbol file
> +as its only argument:
> +
> +@smallexample
> +$ gdb-add-index symfile
> +@end smallexample
I think we should have a cross-reference here to the detailed
description of this script.
> +@node gdb-add-index man
> +@heading gdb-add-index
Please add an index entry here:
@pindex gdb-add-index
> +@c man begin DESCRIPTION gdb-add-index
> +When GDB finds a symbol file, it scans the symbols in the file in order
> +to construct an internal symbol table. This lets most GDB operations
> +work quickly--at the cost of a delay early on. For large programs,
> +this delay can be quite lengthy, so GDB provides a way to build an
> +index, which speeds up startup.
Please use @value{GDBN} instead of a literal "GDB".
> +To determine whether a file contains such an index, use the command
> +@command{readelf -S filename}: the index is stored in a section named
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Commands typed by the user should have the @kbd markup, not @command.
The latter is for names of shell commands, i.e. in general file names
of executable programs and scripts.
> +@code{.gdb_index}. Note that the index is never generated for files that do
^^^^^^^^^^^^^^^^^
File names should have the @file markup.
> +not contain DWARF debug information (sections named @code{.debug_*}).
I think this sentence is too obscure. I think we should say
explicitly that the index can only be produced on systems which use
ELF binaries and DWARF debug info. E.g., users of GDB on MS-Windows
should understand from this that they cannot use this feature.
> +@command{gdb-add-index} uses @value{GDBN} and @command{objdump} found
> +in the @code{PATH} environment variable. If you want to use different
^^^^^^^^^^^
Environment variables should have the @env markup.
> +versions of these programs, you can specify them through the
> +@code{GDB} and @code{OBJDUMP} environment variables.
Likewise.
> +
> +See more in
> +@ifset man
> +the @value{GDBN} manual in node @code{Index Files}
> +-- shell command @code{info -f gdb -n 'Index Files'}.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@kbd, not @code.
Also, please use quotation "like this", because 'like this' only works
on Posix platforms.
The documentation part is OK with those fixed.
Thanks.
next prev parent reply other threads:[~2018-01-12 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 21:35 Sergio Durigan Junior
2018-01-11 22:27 ` Simon Marchi
2018-01-12 4:18 ` Sergio Durigan Junior
2018-01-12 4:20 ` [PATCH v2] " Sergio Durigan Junior
2018-01-12 9:19 ` Eli Zaretskii
2018-01-12 12:44 ` Simon Marchi
2018-01-12 20:31 ` Sergio Durigan Junior
2018-01-12 8:34 ` Eli Zaretskii [this message]
2018-01-12 16:58 ` [PATCH] " Sergio Durigan Junior
2018-01-12 18:39 ` Eli Zaretskii
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=83vag7329f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=tom@tromey.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