From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Document how GDB searches for files when using -s, -e, and -se options
Date: Fri, 03 Jun 2022 08:35:06 +0300 [thread overview]
Message-ID: <83bkvae2d1.fsf@gnu.org> (raw)
In-Reply-To: <20220602224040.139421-1-kevinb@redhat.com> (message from Kevin Buettner via Gdb-patches on Thu, 2 Jun 2022 15:40:40 -0700)
> Date: Thu, 2 Jun 2022 15:40:40 -0700
> From: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
>
> GDB's documentation of the 'file' command says:
>
> If you do not specify a directory and the file is not found in the
> GDB working directory, GDB uses the environment variable PATH as a
> list of directories to search, just as the shell does when looking
> for a program to run.
>
> The same is true for files specified via commandline options -s, -e,
> and -se.
>
> This commit adds similar text to the section of the manual which
> discusses these commandline options.
Thanks. I don't think we need to repeat the same description in the
"File Options" section, we just need to mention this shortly and add a
cross-reference to where the 'file' command's description explains
that.
> +For the @samp{-s}, @samp{-e}, and @samp{-se} options, and their long
> +form equivalents, if @var{file} does not specify a directory as a
> +component of the filename and the file is not found in the
> +@value{GDBN} working directory, @value{GDBN} uses the environment
> +variable @env{PATH} as a list of directories to search, just as the
> +shell does when looking for a program to run. The search algorithm
> +used for these options is identical to that used by the
> +@code{symbol-file}, @code{exec-file}, and @code{file} commands.
Could you please rewrite the above to be shorter and have a
cross-reference?
prev parent reply other threads:[~2022-06-03 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 22:40 Kevin Buettner
2022-06-03 5:35 ` Eli Zaretskii [this message]
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=83bkvae2d1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).