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/
Home Products Support Community News


[Xen-devel] Re: How to use valgrind to detect xen hypervisor's memory le

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: How to use valgrind to detect xen hypervisor's memory leak
From: hellokitty <zhuce5555@xxxxxxx>
Date: Fri, 15 Jul 2011 02:15:36 -0700 (PDT)
Delivery-date: Fri, 15 Jul 2011 02:16:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1310714382.11556.6.camel@xxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1310697774774-4589174.post@xxxxxxxxxxxxx> <1310714382.11556.6.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> Please post your modified version of the patch. 
My patch is in the attach file named  xen_patch.patch 

> You seem to have missed step 0) which is to regenerate configure and
> Makefile.* using autoconf/automake as I described in a previous mail. 
Oh , here before i run 
                  1)     ./configure --with-xen=/usr/include/xen/     &&  
                  2)     make && make install 
 i had run automake/autoconf tool , and the errors still like what i got .
So how to fix it ?

> Wait, are you trying to use valgrind on the hypervisor itself?
> The Xen hypervisor is an "Operating System" and runs on bare metal --
> you can't run it as a process under Linux and therefore you cannot run a
> tool like valgrind on it.

> The valgrind support in my patch is useful for debugging the Xen
> toolstack (e.g. "xl"), but not the hypervisor itself.

Oh , I know that, maybe i didn't express the right meaning . Now , i am more
clearer . Yes , what i want to detect is the Xen toolstack's memory leak not
the hypervisor itself . 

and so suppose that i come to the third step, is it right to use the command
to do the detection ?
"valgrind --tool=memcheck --leak-check=yes xm" 

and more does someone have the valgrind tool support for hypervisor well ,
can you send me one ?

Thank you and best wishes .

View this message in context: 
Sent from the Xen - Dev mailing list archive at Nabble.com.

Xen-devel mailing list