From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc patch] Use plural for global debug info dir(s)
Date: Sat, 12 May 2012 09:31:00 -0000 [thread overview]
Message-ID: <83likxycav.fsf@gnu.org> (raw)
In-Reply-To: <20120512090227.GA20327@host2.jankratochvil.net>
> Date: Sat, 12 May 2012 11:02:27 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> since
> commit 36ae52d16cc9d38cfe317a79bb5d63c624359154
> Author: Jan Kratochvil <jan.kratochvil@redhat.com>
> Date: Mon Nov 2 14:59:48 2009 +0000
>
> GDB supports multiple paths specified in 'set debug-file-directory'.
> Documentation is still inconsistent in this regard.
Thanks for catching this.
> For the ``debug link'' method, @value{GDBN} looks up the named file in
> the directory of the executable file, then in a subdirectory of that
> directory named @file{.debug}, and finally under the global debug
> -directory, in a subdirectory whose name is identical to the leading
> +directories, in a subdirectory whose name is identical to the leading
> directories of the executable's absolute file name.
I would rephrase slightly
... and finally under each one of the global debug
directories, in a subdirectory whose name is identical to the leading
directories of the executable's absolute file name.
> For the ``build ID'' method, @value{GDBN} looks in the
> -@file{.build-id} subdirectory of the global debug directory for a file
> +@file{.build-id} subdirectory of the global debug directories for a file
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Likewise here: "of each one of the global debug directories".
> -@code{abcdef1234}. If the global debug directory is
> +@code{abcdef1234}. If the global debug directories path component is
> @file{/usr/lib/debug}, then @value{GDBN} will look for the following
> debug information files, in the indicated order:
If the list of the global debug directories includes
@file{/usr/lib/debug}, then @value{GDBN} will look ...
> -You can set the global debugging info directory's name, and view the
> +You can set the global debugging info directories, and view the
> name @value{GDBN} is currently using.
^^^^
I would use "list" here, as it's no longer a single name.
OK with those changes.
next prev parent reply other threads:[~2012-05-12 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 9:02 Jan Kratochvil
2012-05-12 9:31 ` Eli Zaretskii [this message]
2012-05-12 14:21 ` [commit] " Jan Kratochvil
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=83likxycav.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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