From: Nick Gasson <nick@nickg.me.uk>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] libdwfl: add dwfl_local_find_debuginfo callback
Date: Sun, 04 Jul 2021 22:12:20 +0800 [thread overview]
Message-ID: <87mtr2jhh7.fsf@nickg.me.uk> (raw)
In-Reply-To: <YN+MS8MMESxnRnsa@wildebeest.org>
Hi Mark,
On 03/07/21 05:59 am, Mark Wielaard wrote:
>
> I wonder if we can use the Dwfl_Callbacks debuginfo_path for this
> instead of introducing a dwfl_standard_find_debuginfo variant. That
> might make things a bit more configurable.
>
> Something like the following maybe:
>
> - If the last path element is "@" then the debuginfo client won't be used.
> - If the last path element is "@{URLs}" (space separated) then the debuginfo client
> will be used with to given URLs.
> - If there is no path element starting with @ then the default debuginfo client
> will be used after all local searches failed (or not when DEBUGINFOD_URLS isn't set).
>
> Does that sound helpful? Does it make sense to make things configurable like this?
>
Thanks for the reply. Yes I think this will work fine for my case.
--
Nick
prev parent reply other threads:[~2021-07-04 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 3:27 Nick Gasson
2021-07-02 21:59 ` Mark Wielaard
2021-07-04 14:12 ` Nick Gasson [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=87mtr2jhh7.fsf@nickg.me.uk \
--to=nick@nickg.me.uk \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).