From: Alex Lindsay <alexlindsay239@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Fix memory leak in cp-support.c (cp_canonicalize_string)
Date: Mon, 07 Aug 2017 20:18:00 -0000 [thread overview]
Message-ID: <20170807201821.25207-1-alexlindsay239@gmail.com> (raw)
Formerly, in cp_canonicalize_string in cp-support.c, the return value of
cp_comp_to_string was never freed, creating a sizable memory leak detectable
with valgrind. This patch fixes the leak. However, a longer term solution
would be to change the return type of cp_comp_to_string to
gdb::unique_xmalloc_ptr<char>.
---
gdb/ChangeLog | 5 +++++
gdb/cp-support.c | 4 +++-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 92c573d76b..e0c43c6185 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2017-08-07 Alex Lindsay <alexlindsay239@gmail.com>
+
+ * cp-support.c (cp_canonicalize_string): Free return value of
+ cp_comp_to_string
+
2017-08-03 Tom Tromey <tom@tromey.com>
* utils.c (make_cleanup_freeargv, do_freeargv, gdb_buildargv):
diff --git a/gdb/cp-support.c b/gdb/cp-support.c
index df9a563508..ffbfd62ee0 100644
--- a/gdb/cp-support.c
+++ b/gdb/cp-support.c
@@ -566,7 +566,9 @@ cp_canonicalize_string (const char *string)
return std::string ();
estimated_len = strlen (string) * 2;
- std::string ret = cp_comp_to_string (info->tree, estimated_len);
+ char *ret_char = cp_comp_to_string (info->tree, estimated_len);
+ std::string ret = ret_char;
+ xfree (ret_char);
if (ret.empty ())
{
--
2.11.0
next reply other threads:[~2017-08-07 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 20:18 Alex Lindsay [this message]
2017-08-09 11:40 ` Yao Qi
2017-08-09 12:09 ` Pedro Alves
2017-08-09 12:31 ` Pedro Alves
2017-08-09 13:27 ` Pedro Alves
2017-08-09 13:41 ` Yao Qi
2017-08-09 14:10 ` Pedro Alves
2017-08-09 13:24 ` Alex Lindsay
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=20170807201821.25207-1-alexlindsay239@gmail.com \
--to=alexlindsay239@gmail.com \
--cc=gdb-patches@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