From: "mark at klomp dot org" <email@example.com>
Subject: [Bug libdw/29434] Memory leak in `dwarf_getscopes`
Date: Thu, 04 Aug 2022 15:57:37 +0000 [thread overview]
Message-ID: <bug-29434-10460-MbyxaGfpt8@http.sourceware.org/bugzilla/> (raw)
--- Comment #5 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Mark Wielaard from comment #3)
> But if the result is zero I don't believe I fully understand yet how the
> leak happens.
So I believe this may happen if we found an inlined subroutine with pc_record,
but then don't find the abstract origin DIE with origin_match.
That does feels like it should be an error, but (currently) isn't.
Maybe this happens if the reference to the abstract origin is in a partial unit
that isn't imported into the current CU.
It would be really nice to have an example of the DIE tree when this happens.
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-04 15:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 16:07 [Bug libdw/29434] New: " godlygeek at gmail dot com
2022-08-04 14:30 ` [Bug libdw/29434] " mark at klomp dot org
2022-08-04 14:43 ` pablogsal at gmail dot com
2022-08-04 15:13 ` mark at klomp dot org
2022-08-04 15:52 ` pablogsal at gmail dot com
2022-08-04 15:57 ` mark at klomp dot org [this message]
2022-08-04 16:05 ` pablogsal at gmail dot com
2022-08-04 16:07 ` pablogsal at gmail dot com
2022-08-04 16:11 ` pablogsal at gmail dot com
2022-08-29 15:28 ` mark at klomp dot org
2022-10-27 20:37 ` mark at klomp dot org
2022-11-03 16:21 ` pablogsal at gmail dot com
2022-11-03 16:22 ` pablogsal at gmail dot com
2022-11-03 16:44 ` pablogsal at gmail dot com
2022-11-03 16:45 ` pablogsal at gmail dot com
2022-11-03 16:58 ` pablogsal at gmail dot com
2022-12-21 13:06 ` mark at klomp dot org
2023-02-22 17:18 ` mark at klomp dot org
2023-02-22 22:41 ` mark at klomp dot org
2023-02-28 11:38 ` mark at klomp dot org
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).