From: Godmar Back <godmar@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Ian Pilcher via Libc-help <libc-help@sourceware.org>,
Ian Pilcher <arequipeno@gmail.com>
Subject: Re: Bug or not? printf allocates buffer & never frees it
Date: Wed, 17 Mar 2021 16:47:31 -0400 [thread overview]
Message-ID: <CAB4+JY+JKtkHwernq6OPf7arRzA_XGDfG37hzvzS8=P-0N8fzQ@mail.gmail.com> (raw)
In-Reply-To: <87h7l91xnu.fsf@oldenburg.str.redhat.com>
On Wed, Mar 17, 2021 at 1:46 PM Florian Weimer via Libc-help
<libc-help@sourceware.org> wrote:
>
> 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.
>
Since you called this a `leak`, may I ask a question that is
tangentially related?
Is GNU libc designed to be used in environments that do not deallocate
all memory upon exit(), i.e., environments that can call exit()
multiple times without being provided with a fresh heap each time? I
understand ISO C allows this and POSIX is quiet on this specific
issue. Is complete deallocation of one-time buffers before exit() a
design goal of GNU libc?
- Godmar
next prev parent reply other threads:[~2021-03-17 20:47 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
2021-03-17 20:29 ` Ian Pilcher
2021-03-17 20:47 ` Godmar Back [this message]
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='CAB4+JY+JKtkHwernq6OPf7arRzA_XGDfG37hzvzS8=P-0N8fzQ@mail.gmail.com' \
--to=godmar@gmail.com \
--cc=arequipeno@gmail.com \
--cc=fweimer@redhat.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).