This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libbacktrace/88063] Libbacktrace leak on dwarf read failure
- From: "vries at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 16 Nov 2018 16:18:00 +0000
- Subject: [Bug libbacktrace/88063] Libbacktrace leak on dwarf read failure
- Auto-submitted: auto-generated
- References: <bug-88063-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88063
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> However, the allocation and deallocation is done in a loop over units, so if
> find_address_ranges succeeds for the first unit, but fails for the second,
> then only the first struct unit is freed, and the second struct unit is
> leaked.
Sorry, that should be the other way around: "then only the second struct unit
is freed, and the first struct unit is leaked. "