public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage-utils:master commit in: tests/atom_explode/
Date: Fri, 29 Mar 2024 10:58:40 +0000 (UTC)	[thread overview]
Message-ID: <1711709905.06d9fb823e99cce2c66c5c4888b91538e66d166e.grobian@gentoo> (raw)

commit:     06d9fb823e99cce2c66c5c4888b91538e66d166e
Author:     Boris Staletic <boris.staletic <AT> protonmail <DOT> com>
AuthorDate: Thu Mar 28 20:30:40 2024 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Fri Mar 29 10:58:25 2024 +0000
URL:        https://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=06d9fb82

tests: avoid leaking buf after exiting the loop in atom_explode

Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>

 tests/atom_explode/test.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/atom_explode/test.c b/tests/atom_explode/test.c
index b794d3b..ff1c58d 100644
--- a/tests/atom_explode/test.c
+++ b/tests/atom_explode/test.c
@@ -64,6 +64,7 @@ int main(int argc, char *argv[])
 			boom(a, buf);
 			atom_implode(a);
 		}
+		free(buf);
 	}
 
 	return EXIT_SUCCESS;


             reply	other threads:[~2024-03-29 10:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 10:58 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-10 10:09 [gentoo-commits] proj/portage-utils:master commit in: tests/atom_explode/ Fabian Groffen
2019-03-20  7:57 Fabian Groffen
2018-08-01 12:18 Fabian Groffen
2018-05-18 18:30 Fabian Groffen
2018-03-30 18:27 Fabian Groffen
2016-02-14  1:26 Mike Frysinger
2015-11-26  8:59 Mike Frysinger
2015-02-21  0:00 Mike Frysinger

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=1711709905.06d9fb823e99cce2c66c5c4888b91538e66d166e.grobian@gentoo \
    --to=grobian@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