From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/27405] libdw_get_srcfiles should not imply srclines
Date: Thu, 11 Apr 2024 16:40:33 +0000 [thread overview]
Message-ID: <bug-27405-10460-uRcw9Q8EII@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27405-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27405
Aaron Merey <amerey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #3 from Aaron Merey <amerey at redhat dot com> ---
Fixed in the following commit:
commit d4b0848be5f575ff9464fee12ce7be416e4fb392
Author: Aaron Merey <amerey@redhat.com>
Date: Mon Mar 25 15:57:25 2024 -0400
libdw: dwarf_getsrcfiles should not imply dwarf_getsrclines
dwarf_getsrcfiles causes line data to be read in addition to file data.
This is wasteful for programs which only need file or directory names.
Debuginfod server is one such example.
Fix this by moving the srcfile reading in read_srclines into a separate
function read_srcfiles. This change improves debuginfod server's max
resident set size by up to 75% during rpm indexing.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-04-11 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 16:18 [Bug libdw/27405] New: " fche at redhat dot com
2021-02-12 16:24 ` [Bug libdw/27405] " mark at klomp dot org
2024-03-29 1:14 ` amerey at redhat dot com
2024-04-11 16:40 ` amerey at redhat dot com [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=bug-27405-10460-uRcw9Q8EII@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).