WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH][XENTOP] fix xentop memory leak

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH][XENTOP] fix xentop memory leak
From: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Date: Mon, 02 Apr 2007 12:31:05 +0900
Delivery-date: Mon, 02 Apr 2007 04:33:11 +0100
Envelope-to: Keir.Fraser@xxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This patch fixes xentop memory leak.

Signed-off-by: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>

I try to use valgrind on x86 with followin options
valgrind --leak-check=full --show-reachable=yes xentop
I found following message.(see item "definitely lost").
With this patch, it fixes the error message value(bytes and blocks)
goes to 0.

==31232==
==31232== 12 bytes in 3 blocks are definitely lost in loss record 2 of 11
==31232==    at 0x40224E5: malloc (vg_replace_malloc.c:149)
==31232==    by 0x804A326: top (xentop.c:957)
==31232==
==31232== LEAK SUMMARY:
==31232==    definitely lost: 12 bytes in 3 blocks.
==31232==      possibly lost: 0 bytes in 0 blocks.
==31232==    still reachable: 5,534 bytes in 15 blocks.
==31232==         suppressed: 0 bytes in 0 blocks.
==31232== Reachable blocks (those to which a pointer was found) are not shown.
==31232== To see them, rerun with: --leak-check=full --show-reachable=yes


Thanks
Atsushi SAKAI
 

Attachment: fix_xentop_memory_leak.patch
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH][XENTOP] fix xentop memory leak, Atsushi SAKAI <=