From: Luis Machado <luis.machado@linaro.org>
To: Ali Tamur <tamur@google.com>, gdb-patches@sourceware.org
Cc: Nitika.Achra@amd.com, JiniSusan.George@amd.com
Subject: Re: [PATCH] Search .dwo in the binary directory.
Date: Tue, 18 Feb 2020 02:33:00 -0000 [thread overview]
Message-ID: <63be4d46-9c25-7deb-a7cc-69276cf740f8@linaro.org> (raw)
In-Reply-To: <20200213061903.83384-1-tamur@google.com>
Hi,
On 2/13/20 3:19 AM, Ali Tamur via gdb-patches wrote:
> .dwo files generated by the compiler usually resides in the same directory as
> the generated binary itself. Add that binary to the list of directories to
> search when searching for the .dwo file.
Thanks. This seems to be aligned with what find_separate_debug_file does:
/* First try in the same directory as the original file. */
std::string debugfile = dir;
debugfile += debuglink;
I guess you meant "Add that binary's path to the list ...".
>
> gdb/ChangeLog:
>
> * dwarf2/read.c (try_open_dwop_file): Include binary directory to
> the list of directories to search. Search the path also when looking
> for a .dwo file.
> ---
> gdb/dwarf2/read.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
> index 7edbd9d7df..39f583e758 100644
> --- a/gdb/dwarf2/read.c
> +++ b/gdb/dwarf2/read.c
> @@ -12012,9 +12012,14 @@ try_open_dwop_file (struct dwarf2_per_objfile *dwarf2_per_objfile,
> else
> search_path = debug_file_directory;
>
> + /* Add the directory of the binary to the search list. */
> + search_path_holder.reset(
> + concat (ldirname (dwarf2_per_objfile->objfile->original_name).c_str (),
> + dirname_separator_string, search_path, (char *) NULL));
> + search_path = search_path_holder.get ();
> +
> openp_flags flags = OPF_RETURN_REALPATH;
> - if (is_dwp)
> - flags |= OPF_SEARCH_IN_PATH;
> + flags |= OPF_SEARCH_IN_PATH;
This was the only use of is_dwp. Now the parameter is unused in
try_open_dwop_file and this and other functions should be updated. Do
you know what is_dwp is originally for? Other than telling the function
we're interested in reading a dwp file?
I see it was added back in 2012 by commit
80626a55b99a0cb91546f334fc683f7a9f351101.
>
> gdb::unique_xmalloc_ptr<char> absolute_name;
> desc = openp (search_path, flags, file_name,
>
next prev parent reply other threads:[~2020-02-18 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 6:19 Ali Tamur via gdb-patches
2020-02-18 2:33 ` Luis Machado [this message]
2020-03-13 13:43 ` Tom Tromey
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=63be4d46-9c25-7deb-a7cc-69276cf740f8@linaro.org \
--to=luis.machado@linaro.org \
--cc=JiniSusan.George@amd.com \
--cc=Nitika.Achra@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=tamur@google.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).