[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: [PATCHv2] valgrind support for Xen privcmd ioctls / hypercalls
Hi , lan :
1. Yes , In my first email i fix some errors to let your patch match valgrind-3.6.1 . My patch is nearly the same as yours. only some line numbers is different . And my patch is xen_patch.patch.
2. after patch it . this time i use autoconf/automake inside valgrind-3.6.1 and run "./configure --with-xen=/usr/include/xen/" and the output is file : output_message.txt 3, Now I run make , it has the error messages, and is in the file error_message.txt in the attach . 4, I am now doing a research about the memory leak of hypervisor of xen in my college with my teacher . and i wonder if you have the valgrind tool support for xen hypervisor ? and if you have the valgrind tool support for hypervisor well , can you give me one ? I need the tool to finish my job however i can't handle it well .....sigh... 5, another question is : if i have the valgrind tool support for hypervisor , how to use the memcheck tool to detect the memory leak of xen hypervisor ? i know how to use the tool to detect normal binary file but i don't know how to detect xen hypervisor . for example , there is a normal c file name test.c . first use "gcc -g -o test test.c" to produce binary file test . then use "valgrind --tool=memcheck --leak-check=yes ./test" to detect the memory leak of "test" . however , how to use the memcheck tool to do my job ? 1) first compile the xen_4.1.1 src files ? -----------------------> will produce a binary file , say it /usr/src/xen-4.0.0/xen/xen 2) second how to use your valgrind tool? ---------------------> run valgrind --tool=memcheck --leak-check=full ./xen ? is this right ?
Thank you !
View this message in context: http://xen.1045712.n5.nabble.com/PATCHv2-valgrind-support-for-Xen-privcmd-ioctls-hypercalls-tp2640861p4568310.html Sent from the Xen - Dev mailing list archive at Nabble.com.
Attachment:
xen_patch.patch
Description: Binary data
Attachment:
output_message.txt
Description: Text document
Attachment:
error_message.txt
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|