public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Document how GDB searches for files when using -s, -e, and -se options Date: Tue, 21 Jun 2022 16:47:58 +0000 (GMT) [thread overview] Message-ID: <20220621164758.85A623858C51@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=bfda149dc1b0376f8cb4c423790246794c7ee873 commit bfda149dc1b0376f8cb4c423790246794c7ee873 Author: Kevin Buettner <kevinb@redhat.com> Date: Thu Jun 2 15:26:38 2022 -0700 Document how GDB searches for files when using -s, -e, and -se options 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 a cross reference to the file command for these options. Diff: --- gdb/doc/gdb.texinfo | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index b3e995f166b..38ae249f62d 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -962,6 +962,11 @@ If @value{GDBN} has not been configured to included core file support, such as for most embedded targets, then it will complain about a second argument and ignore it. +For the @samp{-s}, @samp{-e}, and @samp{-se} options, and their long +form equivalents, the method used to search the file system for the +symbol and/or executable file is the same as that used by the +@code{file} command. @xref{Files, ,file}. + Many options have both long and short forms; both are shown in the following list. @value{GDBN} also recognizes the long forms if you truncate them, so long as enough of the option is present to be unambiguous.
reply other threads:[~2022-06-21 16:47 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220621164758.85A623858C51@sourceware.org \ --to=kevinb@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).