From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27633] low mem memory leaks
Date: Tue, 23 Mar 2021 11:15:48 +0000 [thread overview]
Message-ID: <bug-27633-11298-mbpmRhPE1p@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27633-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27633
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
This fixes it:
...
diff --git a/dwz.c b/dwz.c
index 4fc01a3..3dd4d5e 100644
--- a/dwz.c
+++ b/dwz.c
@@ -6628,7 +6628,8 @@ read_debug_info (DSO *dso, int kind, unsigned int
*die_count)
if (dup_htab == NULL)
dwz_oom ();
}
- if (unlikely (op_multifile || rd_multifile || fi_multifile || low_mem))
+ if (meta_abbrev_htab == NULL
+ && unlikely (op_multifile || rd_multifile || fi_multifile || low_mem))
{
meta_abbrev_htab
= htab_try_create (500, meta_abbrev_hash, meta_abbrev_eq,
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-23 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 11:05 [Bug default/27633] New: " vries at gcc dot gnu.org
2021-03-23 11:15 ` [Bug default/27633] " vries at gcc dot gnu.org
2021-03-23 11:15 ` vries at gcc dot gnu.org [this message]
2021-03-23 13:19 ` vries at gcc dot gnu.org
2021-03-24 17:08 ` vries at gcc dot gnu.org
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-27633-11298-mbpmRhPE1p@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).