| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: How to use valgrind to detect xen hypervisor's memory le
> I downloaded 3.6.1, applied the attached patch and ran:
> aclocal && autoheader && automake -a && autoconf (per the autogen.sh in
> valgrind SVN)
> Then I ran:
> ./configure --with-xen && make
> and it built fine (since it defaults to looking in /usr/include for
> headers).
> I also tried "./configure --with-xen=/usr/include" which also worked.
> However --with-xen=/usr/include/xen (as you had) did not work because
> the path is wrong and should not include the final /xen (since the
> #includes in the code are of the form <xen/thing.h>), although my
> error
> messages in this case were not the same as yours.
Here , i follow your step , and use the "X" patch you uploaded , and run
"aclocal && autoheader && automake -a && autoconf " ,goes well and then run
"./configure --with-xen && make" , and when it comes to make , it has the
errors below :
Making all in coregrind
make[2]: Entering directory `/home/popo/valgrind-3.6.1/coregrind'
make all-am
make[3]: Entering directory `/home/popo/valgrind-3.6.1/coregrind'
gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1
-DVGO_linux=1 -DVGP_x86_linux=1 -I../coregrind
-DVG_LIBDIR="\"/usr/local/lib/valgrind"\" -DVG_PLATFORM="\"x86-linux\""
-m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow
-Wpointer-arith -Wstrict-prototypes -Wmissing-declarations
-Wno-format-zero-length -fno-strict-aliasing -Iyes -Wno-long-long
-Wno-pointer-sign -fno-stack-protector -MT
libcoregrind_x86_linux_a-syswrap-xen.o -MD -MP -MF
.deps/libcoregrind_x86_linux_a-syswrap-xen.Tpo -c -o
libcoregrind_x86_linux_a-syswrap-xen.o `test -f 'm_syswrap/syswrap-xen.c' ||
echo './'`m_syswrap/syswrap-xen.c
m_syswrap/syswrap-xen.c: In function
‘vgSysWrap_xen_ioctl_privcmd_hypercall_before’:
m_syswrap/syswrap-xen.c:119: error: ‘MMUEXT_MARK_SUPER’ undeclared (first
use in this function)
m_syswrap/syswrap-xen.c:119: error: (Each undeclared identifier is reported
only once
m_syswrap/syswrap-xen.c:119: error: for each function it appears in.)
m_syswrap/syswrap-xen.c:120: error: ‘MMUEXT_UNMARK_SUPER’ undeclared (first
use in this function)
m_syswrap/syswrap-xen.c:136: error: ‘MMUEXT_FLUSH_CACHE_GLOBAL’ undeclared
(first use in this function)
m_syswrap/syswrap-xen.c:263: error: ‘XEN_SYSCTL_cpupool_op’ undeclared
(first use in this function)
m_syswrap/syswrap-xen.c:264: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:264: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:266: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:267: error: ‘XEN_SYSCTL_CPUPOOL_OP_CREATE’
undeclared (first use in this function)
m_syswrap/syswrap-xen.c:268: error: ‘XEN_SYSCTL_CPUPOOL_OP_DESTROY’
undeclared (first use in this function)
m_syswrap/syswrap-xen.c:269: error: ‘XEN_SYSCTL_CPUPOOL_OP_INFO’ undeclared
(first use in this function)
m_syswrap/syswrap-xen.c:270: error: ‘XEN_SYSCTL_CPUPOOL_OP_ADDCPU’
undeclared (first use in this function)
m_syswrap/syswrap-xen.c:271: error: ‘XEN_SYSCTL_CPUPOOL_OP_RMCPU’ undeclared
(first use in this function)
m_syswrap/syswrap-xen.c:272: error: ‘XEN_SYSCTL_CPUPOOL_OP_MOVEDOMAIN’
undeclared (first use in this function)
m_syswrap/syswrap-xen.c:273: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:273: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:276: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:277: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:277: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:279: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:280: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:280: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:282: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:283: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:284: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:284: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c: In function
‘vgSysWrap_xen_ioctl_privcmd_hypercall_after’:
m_syswrap/syswrap-xen.c:558: error: ‘XEN_SYSCTL_cpupool_op’ undeclared
(first use in this function)
m_syswrap/syswrap-xen.c:559: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:559: error: ‘XEN_SYSCTL_CPUPOOL_OP_CREATE’
undeclared (first use in this function)
m_syswrap/syswrap-xen.c:560: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:560: error: ‘XEN_SYSCTL_CPUPOOL_OP_INFO’ undeclared
(first use in this function)
m_syswrap/syswrap-xen.c:561: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:561: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:562: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:563: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:563: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:564: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:564: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:566: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:567: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:567: error: ‘XEN_SYSCTL_CPUPOOL_OP_FREEINFO’
undeclared (first use in this function)
m_syswrap/syswrap-xen.c:568: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:568: error: ‘union <anonymous>’ has no member named
‘cpupool_op’
m_syswrap/syswrap-xen.c:576: error: ‘struct xen_sysctl_physinfo’ has no
member named ‘nr_nodes’
m_syswrap/syswrap-xen.c:576: error: ‘struct xen_sysctl_physinfo’ has no
member named ‘nr_nodes’
m_syswrap/syswrap-xen.c:658: error: ‘struct xen_domctl_getdomaininfo’ has no
member named ‘cpupool’
m_syswrap/syswrap-xen.c:658: error: ‘struct xen_domctl_getdomaininfo’ has no
member named ‘cpupool’
make[3]: *** [libcoregrind_x86_linux_a-syswrap-xen.o] Error 1
make[3]: Leaving directory `/home/popo/valgrind-3.6.1/coregrind'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/popo/valgrind-3.6.1/coregrind'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/popo/valgrind-3.6.1'
make: *** [all] Error 2
How about you ? and i don't know how to fix it yet .....
--
View this message in context:
http://xen.1045712.n5.nabble.com/How-to-use-valgrind-to-detect-xen-hypervisor-s-memory-leak-tp4589174p4593243.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home