Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10201] buildroot-2017.08-rc1/toolchain/toolchain-wrapper.c:192]: (error) Memory leak:
Date: Fri, 11 Aug 2017 14:15:45 +0000	[thread overview]
Message-ID: <bug-10201-163-Dz1Sjif4hl@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10201-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10201

Arnout Vandecappelle <arnout@mind.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
Your static analyser is weird, because there are a few other things which
aren't freed either: relbasedir, absbasedir in different code paths.

However, we do this by choice. Freeing things before exiting is useless, since
the OS will implicitly free everything when the program exits. That's why e.g.
valgrind doesn't report these as real memory leaks (because they are still
reachable).

So no, this is not a memory leak.

For consistency, the free(args) at the end should be removed, but that's a
different issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2017-08-11 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09 20:18 [Buildroot] [Bug 10201] New: buildroot-2017.08-rc1/toolchain/toolchain-wrapper.c:192]: (error) Memory leak: bugzilla at busybox.net
2017-08-11 14:15 ` bugzilla at busybox.net [this message]

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-10201-163-Dz1Sjif4hl@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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