From: "Alon Bar-Lev (alonbl)" <alonbl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-crypt/pinentry/files: pinentry-0.9.1-memleak.patch
Date: Sun, 3 May 2015 15:17:14 +0000 (UTC) [thread overview]
Message-ID: <20150503151716.CD8519CC@oystercatcher.gentoo.org> (raw)
alonbl 15/05/03 15:17:14
Added: pinentry-0.9.1-memleak.patch
Log:
Version bump, bug#548456
(Portage version: 2.2.18/cvs/Linux x86_64, signed Manifest commit with key BF20DC51)
Revision Changes Path
1.1 app-crypt/pinentry/files/pinentry-0.9.1-memleak.patch
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-crypt/pinentry/files/pinentry-0.9.1-memleak.patch?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-crypt/pinentry/files/pinentry-0.9.1-memleak.patch?rev=1.1&content-type=text/plain
Index: pinentry-0.9.1-memleak.patch
===================================================================
From 03e4207f11e228a4c079af991f82507539793bae Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Date: Tue, 28 Apr 2015 13:01:16 -0400
Subject: [PATCH] fix small memory leak in pinentry-curses
* pinentry/pinentry-curses.c: free internally allocated local string.
---
pinentry/pinentry-curses.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/pinentry/pinentry-curses.c b/pinentry/pinentry-curses.c
index 4b7080e..043f8a9 100644
--- a/pinentry/pinentry-curses.c
+++ b/pinentry/pinentry-curses.c
@@ -199,6 +199,8 @@ utf8_to_local (char *lc_ctype, char *string)
memset (&ps, 0, sizeof(mbstate_t));
mbsrtowcs (wcs, &p, len, &ps);
+ free (local);
+
leave:
if (old_ctype)
{
--
2.1.4
next reply other threads:[~2015-05-03 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 15:17 Alon Bar-Lev (alonbl) [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-07 15:31 [gentoo-commits] gentoo-x86 commit in app-crypt/pinentry/files: pinentry-0.9.1-memleak.patch Kristian Fiskerstrand (k_f)
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=20150503151716.CD8519CC@oystercatcher.gentoo.org \
--to=alonbl@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