From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27633] New: low mem memory leaks
Date: Tue, 23 Mar 2021 11:05:41 +0000 [thread overview]
Message-ID: <bug-27633-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27633
Bug ID: 27633
Summary: low mem memory leaks
Product: dwz
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
When building dwz with address sanitizer, we run into:
...
$ ./dwz hello -o hello.z -l0
=================================================================
==22607==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 432 byte(s) in 6 object(s) allocated from:
#0 0x7f560af846d8 in __interceptor_calloc (/usr/lib64/libasan.so.4+0xdc6d8)
#1 0x475db1 in htab_try_create /home/vries/dwz/dwz.git/hashtab.c:164
#2 0x406ed6 in read_abbrev /home/vries/dwz/dwz.git/dwz.c:1296
#3 0x42bca9 in read_debug_info /home/vries/dwz/dwz.git/dwz.c:6818
#4 0x4608cb in read_dwarf /home/vries/dwz/dwz.git/dwz.c:13706
#5 0x46ef9a in dwz /home/vries/dwz/dwz.git/dwz.c:15383
#6 0x474a27 in dwz_one_file /home/vries/dwz/dwz.git/dwz.c:16279
#7 0x475951 in main /home/vries/dwz/dwz.git/dwz.c:16450
#8 0x7f560a8f9349 in __libc_start_main (/lib64/libc.so.6+0x24349)
Direct leak of 72 byte(s) in 1 object(s) allocated from:
#0 0x7f560af846d8 in __interceptor_calloc (/usr/lib64/libasan.so.4+0xdc6d8)
#1 0x475db1 in htab_try_create /home/vries/dwz/dwz.git/hashtab.c:164
#2 0x42a8fd in read_debug_info /home/vries/dwz/dwz.git/dwz.c:6634
#3 0x4608cb in read_dwarf /home/vries/dwz/dwz.git/dwz.c:13706
#4 0x46ef9a in dwz /home/vries/dwz/dwz.git/dwz.c:15383
#5 0x474a27 in dwz_one_file /home/vries/dwz/dwz.git/dwz.c:16279
#6 0x475951 in main /home/vries/dwz/dwz.git/dwz.c:16450
#7 0x7f560a8f9349 in __libc_start_main (/lib64/libc.so.6+0x24349)
Indirect leak of 4072 byte(s) in 1 object(s) allocated from:
#0 0x7f560af846d8 in __interceptor_calloc (/usr/lib64/libasan.so.4+0xdc6d8)
#1 0x475dd7 in htab_try_create /home/vries/dwz/dwz.git/hashtab.c:168
#2 0x42a8fd in read_debug_info /home/vries/dwz/dwz.git/dwz.c:6634
#3 0x4608cb in read_dwarf /home/vries/dwz/dwz.git/dwz.c:13706
#4 0x46ef9a in dwz /home/vries/dwz/dwz.git/dwz.c:15383
#5 0x474a27 in dwz_one_file /home/vries/dwz/dwz.git/dwz.c:16279
#6 0x475951 in main /home/vries/dwz/dwz.git/dwz.c:16450
#7 0x7f560a8f9349 in __libc_start_main (/lib64/libc.so.6+0x24349)
Indirect leak of 2928 byte(s) in 6 object(s) allocated from:
#0 0x7f560af846d8 in __interceptor_calloc (/usr/lib64/libasan.so.4+0xdc6d8)
#1 0x475dd7 in htab_try_create /home/vries/dwz/dwz.git/hashtab.c:168
#2 0x406ed6 in read_abbrev /home/vries/dwz/dwz.git/dwz.c:1296
#3 0x42bca9 in read_debug_info /home/vries/dwz/dwz.git/dwz.c:6818
#4 0x4608cb in read_dwarf /home/vries/dwz/dwz.git/dwz.c:13706
#5 0x46ef9a in dwz /home/vries/dwz/dwz.git/dwz.c:15383
#6 0x474a27 in dwz_one_file /home/vries/dwz/dwz.git/dwz.c:16279
#7 0x475951 in main /home/vries/dwz/dwz.git/dwz.c:16450
#8 0x7f560a8f9349 in __libc_start_main (/lib64/libc.so.6+0x24349)
SUMMARY: AddressSanitizer: 7504 byte(s) leaked in 14 allocation(s).
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-23 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 11:05 vries at gcc dot gnu.org [this message]
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
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@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).