From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/30564] New: deduplicate debugedit -l sources output
Date: Mon, 19 Jun 2023 11:47:47 +0000 [thread overview]
Message-ID: <bug-30564-13298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30564
Bug ID: 30564
Summary: deduplicate debugedit -l sources output
Product: debugedit
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debugedit
Assignee: unassigned at sourceware dot org
Reporter: mark at klomp dot org
CC: debugedit at sourceware dot org
Target Milestone: ---
https://inbox.sourceware.org/debugedit/4fd77ae2cbc3fdc194bcd0fc37c0c2f92efb66e6.camel@klomp.org/T/#u
https://sourceware.org/cgit/debugedit/commit/?id=41fc1335b8b364c95a8ee2ed2956bbdfe7957853
find-debuginfo deduplicates the debugedit -l sources output (and must for
multiple debugedit invocations on different object files).
But this could be a little bit more efficient if debugedit itself deduplicated
the sources list itself.
A quick check shows that the number of files output contains ~90% duplicates.
On elfutils eu-readelf debugedit -n -l sources produces 2370 files of which on
246 are unique files.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2023-06-19 11:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-30564-13298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=debugedit@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).