From: Florian Weimer <fweimer@redhat.com>
To: Ian Pilcher via Libc-help <libc-help@sourceware.org>
Cc: Ian Pilcher <arequipeno@gmail.com>
Subject: Re: Bug or not? printf allocates buffer & never frees it
Date: Wed, 17 Mar 2021 18:45:57 +0100 [thread overview]
Message-ID: <87h7l91xnu.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <s2tebb$135j$1@ciao.gmane.io> (Ian Pilcher via Libc-help's message of "Wed, 17 Mar 2021 12:30:19 -0500")
* Ian Pilcher via Libc-help:
> Fedora 33 with glibc-2.32-4.fc33.x86_64.
>
> Simple reproducer:
>
> #include <mcheck.h>
> #include <stdio.h>
>
> int main(void)
> {
> mtrace();
> printf("%d\n", 0);
> muntrace();
> return 0;
> }
>
> Running with MALLOC_TRACE set shows:
>
> Memory not freed:
> -----------------
> Address Size Caller
> 0x0000000000e1d690 0x400 at 0x7f19511d2934
> Is this considered a bug?
What happens if you remove the muntrace call? I suspect you see this
leak because you are specifically telling glibc not to log the
deallocation.
Thanks,
Florian
next prev parent reply other threads:[~2021-03-17 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 17:30 Ian Pilcher
2021-03-17 17:45 ` Florian Weimer [this message]
2021-03-17 20:29 ` Ian Pilcher
2021-03-17 20:47 ` Godmar Back
2021-03-17 21:03 ` Florian Weimer
2021-03-17 19:23 ` Konstantin Kharlamov
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=87h7l91xnu.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=arequipeno@gmail.com \
--cc=libc-help@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).