From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/configure.ac: Add option --with-additional-debug-dirs
Date: Fri, 23 Jun 2023 00:53:09 +0200 [thread overview]
Message-ID: <87jzvvgld6.fsf@linaro.org> (raw)
In-Reply-To: <20230606233118.146167-1-thiago.bauermann@linaro.org>
Thiago Jung Bauermann <thiago.bauermann@linaro.org> writes:
> If you want to install GDB in a custom prefix, have it look for debug info
> in that prefix but also in the distro's default location (typically,
> /usr/lib/debug) and run the GDB testsuite before doing "make install", you
> have a bit of a problem:
>
> Configuring GDB with '--prefix=$PREFIX' sets the GDB 'debug-file-directory'
> parameter to $PREFIX/lib/debug. Unfortunately this precludes GDB from
> looking for distro-installed debug info in /usr/lib/debug. For regular GDB
> use you could set debug-file-directory to $PREFIX:/usr/lib/debug in
> $PREFIX/etc/gdbinit so that GDB will look in both places, but if you want
> to run the testsuite then that doesn't help because in that case GDB runs
> with the '-nx' option.
>
> There's the configure option '--with-separate-debug-dir' to set the default
> value for 'debug-file-directory', but it accepts only one directory and not
> a list. I considered modifying it to accept a list, but it's not obvious
> how to do that because its value is also used by BFD, as well as processed
> for "relocatability".
>
> I thought it was simpler to add a new option to specify a list of
> additional directories that will be appended to the debug-file-directory
> setting.
> ---
> gdb/config.in | 3 +++
> gdb/configure | 19 +++++++++++++++++--
> gdb/configure.ac | 6 ++++++
> gdb/main.c | 5 +++++
> gdb/top.c | 6 ++++++
> 5 files changed, 37 insertions(+), 2 deletions(-)
Ping.
--
Thiago
next prev parent reply other threads:[~2023-06-22 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 23:31 Thiago Jung Bauermann
2023-06-22 22:53 ` Thiago Jung Bauermann [this message]
2023-10-03 18:59 ` Tom Tromey
2023-10-04 18:29 ` Thiago Jung Bauermann
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=87jzvvgld6.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--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).