From: Andreas Schwab <schwab@linux-m68k.org>
To: <5upnzm+87w9w470225qs@sharklasers.com>
Cc: 25364@debbugs.gnu.org
Subject: bug#25364: etags malloc problems
Date: Thu, 05 Jan 2017 16:52:47 +0100 [thread overview]
Message-ID: <87r34h33n4.fsf@linux-m68k.org> (raw)
In-Reply-To: <91a665173f0064eaaf432cb1d52f3dd57635@sharklasers.com> (5upnzm+87w9w470225qs@sharklasers.com's message of "Thu, 05 Jan 2017 03:07:13 +0000")
On Jan 05 2017, <5upnzm+87w9w470225qs@sharklasers.com> wrote:
> ==5176==ERROR: LeakSanitizer: detected memory leaks
>
> Direct leak of 120 byte(s) in 1 object(s) allocated from:
> #0 0x4cba68 in __interceptor_malloc (/tmp/etags/etags+0x4cba68)
> #1 0x5043f8 in xmalloc /tmp/etags/etags.c:7238:18
> #2 0x5036c5 in main /tmp/etags/etags.c:1097:15
> #3 0x7fb31bc332b0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202b0)
>
> Direct leak of 40 byte(s) in 1 object(s) allocated from:
> #0 0x4cba68 in __interceptor_malloc (/tmp/etags/etags+0x4cba68)
> #1 0x5043f8 in xmalloc /tmp/etags/etags.c:7238:18
> #2 0x5036b8 in main /tmp/etags/etags.c:1091:20
> #3 0x7fb31bc332b0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202b0)
>
> Direct leak of 24 byte(s) in 1 object(s) allocated from:
> #0 0x4cba68 in __interceptor_malloc (/tmp/etags/etags+0x4cba68)
> #1 0x5043f8 in xmalloc /tmp/etags/etags.c:7238:18
> #2 0x50447c in concat /tmp/etags/etags.c:6958:18
> #3 0x503706 in main /tmp/etags/etags.c:1109:15
> #4 0x7fb31bc332b0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202b0)
These are all allocations in main, no point in freeing them if the
process is exiting anyway.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-01-05 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 3:07 bug#25364: etags malloc problems 5upnzm+87w9w470225qs
2017-01-05 15:36 ` Eli Zaretskii
2017-01-05 15:52 ` Andreas Schwab [this message]
2017-01-05 16:54 ` Richard Stallman
2019-09-29 15:17 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r34h33n4.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=25364@debbugs.gnu.org \
--cc=5upnzm+87w9w470225qs@sharklasers.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).