public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Merey <amerey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.texinfo: Expand documentation for debuginfod
Date: Sat, 01 May 2021 09:22:35 +0300	[thread overview]
Message-ID: <83mttf9dn8.fsf@gnu.org> (raw)
In-Reply-To: <20210430235048.1371108-1-amerey@redhat.com> (message from Aaron Merey via Gdb-patches on Fri, 30 Apr 2021 19:50:48 -0400)

> Date: Fri, 30 Apr 2021 19:50:48 -0400
> From: Aaron Merey via Gdb-patches <gdb-patches@sourceware.org>
> 
> Add section describing GDB's usage of debuginfod.
> 
> Refer to this new section in the description of the '--with-debuginfod'
> configure option.
> 
> Mention debuginfod in the 'Separate Debug Files' section.
> 
> gdb/doc/ChangeLog:
> 
> 	* gdb.texinfo (Debuginfod): New section.
> 	(Configure Options): Refer to debuginfod section.
> 	(Separate Debug Files): Mention debuginfod.

Thanks, some comments below.

> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -184,6 +184,7 @@ software in general.  We will miss him.
>                                   the operating system
>  * Trace File Format::		GDB trace file format
>  * Index Section Format::        .gdb_index section format
> +* Debuginfod::			Download debugging resources with debuginfod

Please don't use TAB characters in Texinfo sources; use spaces
instead.

> -hex characters, not 10.)
> +hex characters, not 10.) @value{GDBN} can automatically query
> +debuginfod servers using build IDs in order to download separate debug
> +files that cannot be found locally. For more information see
> +@ref{Debuginfod}.

Please leave 2 spaces between sentences, here and elsewhere in your
patch.  We use US English conventions and spelling.

> +If the debug file still has not been found and debuginfod is enabled,
> +@value{GDBN} will attempt to download the file from debuginfod servers.

Please add here a cross-reference to the node which describes
debuginfod (preferably @pxref in parentheses after "debuginfod"), so
that the readers could easily find the relevant information.

Also, I wonder whether "debuginfod" should be in @code everywhere
(except in cross-references and the node name), since I believe we use
that markup for other packages.

> +Used to automatically fetch ELF, DWARF and source files from debuginfod
> +servers using their associated build IDs.
                 ^^^^^
This "their" is ambiguous: it could refer to ELF/DWARF/source files,
or it could refer to debuginfod servers.  FWIW, I think the original
text is better in this regard.

>                                             Enabled by default if
> +libdebuginfod is installed and found at configure time. For more
> +information regarding debuginfod see @ref{Debuginfod}.

"libdebuginfod" should have the @file markup.

> +@node Debuginfod
> +@appendix Download debugging resources with Debuginfod

Please add here the "@cindex debuginfod" index entry.

> +Using the debuginfod client library, libdebuginfod, @value{GDBN} can
                                        ^^^^^^^^^^^^^
@file{libdebuginfod}

> +See @ref{Configure Options,,--with-debuginfod} for instructions on
   ^^^^^^^^
It's better to use @xref here instead of "See @ref".

> +building @value{GDBN} with libdebuginfod. Debuginfod is packaged with
> +elfutils, starting with version 0.178. See
   ^^^^^^^^
@code{elfutils}

> +`https://sourceware.org/elfutils/Debuginfod.html` for more information
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Please use @uref here instead of Markdown-like quoting.

  reply	other threads:[~2021-05-01  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 23:50 Aaron Merey
2021-05-01  6:22 ` Eli Zaretskii [this message]
2021-05-06 17:18   ` Aaron Merey
2021-05-06 17:51     ` 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=83mttf9dn8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=amerey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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).