This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[patch v3 19/23] btrace, linux: fix memory leak when reading branch trace
- From: Markus Metzger <markus dot t dot metzger at intel dot com>
- To: jan dot kratochvil at redhat dot com
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 10 Jun 2013 10:04:52 +0200
- Subject: [patch v3 19/23] btrace, linux: fix memory leak when reading branch trace
- References: <1370851496-32313-1-git-send-email-markus dot t dot metzger at intel dot com>
When it takes more than one iteration to read the BTS trace, the trace from the
previous iteration is leaked. Fix it.
2013-06-10 Markus Metzger <markus.t.metzger@intel.com>
* common/linux-btrace.c (linux_read_btrace): Free trace from
previous iteration.
---
gdb/common/linux-btrace.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/gdb/common/linux-btrace.c b/gdb/common/linux-btrace.c
index 2d0bc45..43f20ee 100644
--- a/gdb/common/linux-btrace.c
+++ b/gdb/common/linux-btrace.c
@@ -548,6 +548,9 @@ linux_read_btrace (struct btrace_target_info *tinfo,
{
data_head = header->data_head;
+ /* Delete any leftover trace from the previous iteration. */
+ VEC_truncate (btrace_block_s, btrace, 0);
+
/* If there's new trace, let's read it. */
if (data_head != tinfo->data_head)
{
--
1.7.1