From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/30000] New: debuginfod-find should have a source-list verb
Date: Fri, 13 Jan 2023 20:55:51 +0000 [thread overview]
Message-ID: <bug-30000-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30000
Bug ID: 30000
Summary: debuginfod-find should have a source-list verb
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Let's implement
% debuginfod-find source-list PATH|BUILDID
so it fetches the debuginfo, then runs the dwarf_getsrcfiles / dwarf_getsrcdirs
/ CU comp_dir traversal, and prints a deduped list of all CUs' source file
lists. An adventurous user can then use that to fetch all source files of a
particular binary.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-01-13 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 20:55 fche at redhat dot com [this message]
2023-01-13 20:58 ` [Bug debuginfod/30000] " serhei at serhei dot io
2023-09-26 15:10 ` [Bug debuginfod/30000] introduce new srcfiles tool fche at redhat dot com
2023-09-26 20:01 ` fche at redhat dot com
2023-10-24 20:00 ` amerey at redhat dot com
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=bug-30000-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).