[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: How to use valgrind to detect xen hypervisor's memory leak
> 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |