public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: libc-help@sourceware.org
Subject: Re: Bug or not? printf allocates buffer & never frees it
Date: Wed, 17 Mar 2021 15:29:52 -0500	[thread overview]
Message-ID: <s2tos0$fj5$1@ciao.gmane.io> (raw)
In-Reply-To: <87h7l91xnu.fsf@oldenburg.str.redhat.com>

On 3/17/21 12:45 PM, Florian Weimer via Libc-help 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.

You are correct.  Blindingly obvious in retrospect.

Thanks!

-- 
========================================================================
                  In Soviet Russia, Google searches you!
========================================================================


  reply	other threads:[~2021-03-17 20:29 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 [this message]
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='s2tos0$fj5$1@ciao.gmane.io' \
    --to=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).