From: Mark Wielaard <mark@klomp.org>
To: Ryan Goldberg <rgoldber@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: One shot mode for debuginfod server
Date: Thu, 27 Oct 2022 15:37:25 +0200 [thread overview]
Message-ID: <a5fa0c3b34f80a11baec921be040834a9b165d73.camel@klomp.org> (raw)
In-Reply-To: <CAE8aAookTcnPJOGGOEsGfO57kqdx0xc_PtgLzpTS23tg1eSBjw@mail.gmail.com>
Hi Ryan,
On Tue, 2022-08-09 at 17:40 -0400, Ryan Goldberg via Elfutils-devel
wrote:
> Here is a patch for a new one-shot mode for the debuginfod server.
> In this mode the first scanning pass of the server will also output
> the found executables' paths and buildids to the given file
> descriptor. This can (and soon will be used in systemtap)
> as an easy way to scan archive files and quickly/easily extract
> information concerning the executables they contain.
I see how this could be useful, but wouldn't it be easier to have a
database query do this?
Cheers,
Mark
prev parent reply other threads:[~2022-10-27 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 21:40 Ryan Goldberg
2022-10-27 13:37 ` Mark Wielaard [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=a5fa0c3b34f80a11baec921be040834a9b165d73.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=rgoldber@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).