public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/libbash:master commit in: src/
Date: Sun,  3 Apr 2011 10:16:11 +0000 (UTC)	[thread overview]
Message-ID: <d30fc4046d0a8875f5e7d9c95560739d65b7a2c8.betelgeuse@gentoo> (raw)

commit:     d30fc4046d0a8875f5e7d9c95560739d65b7a2c8
Author:     Petteri Räty <petsku <AT> petteriraty <DOT> eu>
AuthorDate: Sat Apr  2 16:45:18 2011 +0000
Commit:     Petteri Räty <betelgeuse <AT> gentoo <DOT> org>
CommitDate: Sat Apr  2 16:45:18 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/libbash.git;a=commit;h=d30fc404

Stop variable_printer from leaking memory

We are not releasing antlr datastructures so variable_printer leaked
memory. Now valgrind is happy.

---
 src/libbash.cpp |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/src/libbash.cpp b/src/libbash.cpp
index 60076b5..e821d81 100644
--- a/src/libbash.cpp
+++ b/src/libbash.cpp
@@ -63,6 +63,13 @@ namespace libbash
     plibbashWalker treePsr = libbashWalkerNew(nodes);
     treePsr->start(treePsr);
 
+    treePsr->free(treePsr);
+    nodes->free(nodes);
+    psr->free(psr);
+    tstream->free(tstream);
+    lxr->free(lxr);
+    input->close(input);
+
     for(auto iter = walker->begin(); iter != walker->end(); ++iter)
     {
       variables[iter->first]=std::static_pointer_cast<variable>(iter->second)->get_value<std::string>();



             reply	other threads:[~2011-04-03 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03 10:16 Petteri Räty [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-08  9:44 [gentoo-commits] proj/libbash:master commit in: src/ Petteri Räty
2011-04-02 15:50 Petteri Räty

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=d30fc4046d0a8875f5e7d9c95560739d65b7a2c8.betelgeuse@gentoo \
    --to=betelgeuse@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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