[ltt-dev] Ltt-control-0.37, lttv-0.8.82: core.xml, line 0:invalid character, unrecognized token
Mathieu Desnoyers
compudj at krystal.dyndns.org
Wed Sep 10 18:41:26 EDT 2008
* KokHow.Teh at infineon.com (KokHow.Teh at infineon.com) wrote:
> Hi;
> This is the compatibility combination that I am using:
> 0.8.82
> 0.9.0
> 0.37
> obsolete
> 0.29
> 0.34
> 0.8
> 2.6.20
> ARM, MIPS32/64, powerpc32, powerpc64, ppc, i386, x86_64
> Introduces the LTT serialization library. Cuts the kernel patch size
> from 2M to 500k. Deprecates genevent for kernel instrumentation, but
> keeps backward compatibility with genevent generated code (still used
> for user space tracing). Slightly longer execution time at
> instrumentation site (270ns vs 200ns for 4 bytes write on P4 3GHz), but
> the global advantage of using less memory, and therefore less cache,
> should overweight this cost in cycles. Note : In this version, the
> ltt-probe-* kernel modules and the XML definitions must be kept in sync
> by hand, otherwise, LTTV will detect a size mismatch between the kernel
> trace and the expected event size..
> arm, i686, ia64, m68k, mips, mipsel, x86_64, powerpc 405, powerpc64,
> s390, sparc, sparc64.
> alpha, arm26, avr32, cris, frv, h8300, m32r, m68knommu, parisc, sh,
> sh64, um, v850, xtensa
>
> Could someone please provide more details about the note given?
> Note : In this version, the ltt-probe-* kernel modules and the XML
> definitions must be kept in sync by hand, otherwise, LTTV will detect a
> size mismatch between the kernel trace and the expected event size..
>
> Which LTTng-0.9.0/LTTV files to look out for to maintain the
> sync?
In this old version, you have to keep in sync, by hand, XML descriptions
found in the ltt-control package and the ltt/probes/ltt-probe-*.c files
from the kernel patch when you want to add a new kernel event.
Mathieu
> Thanks.
>
> Regards,
> KH
>
> -----Original Message-----
> From: Mathieu Desnoyers [mailto:compudj at krystal.dyndns.org]
> Sent: Wednesday, August 20, 2008 10:16 PM
> To: Teh Kok How (IFAP DC COM WL SD)
> Cc: ltt-dev at lists.casi.polymtl.ca
> Subject: Re: [ltt-dev] Ltt-control-0.37, lttv-0.8.82: core.xml, line
> 0:invalid character, unrecognized token
>
> Which versino of LTTng patch have you used exactly ?
>
> Did you follow this compatibility list ?
>
> http://ltt.polymtl.ca/svn/trunk/lttv/doc/developer/lttng-lttv-compatibil
> ity.html
>
> Mathieu
>
> * KokHow.Teh at infineon.com (KokHow.Teh at infineon.com) wrote:
> > Hi;
> > The LTTng patch used is for linux-2.6.20. So some of the latest
> stuff
> > like ltt-armall.sh, ltt-serialize.c are missing.....
> >
> > Regards,
> > KH
> >
> > > _____________________________________________
> > > From: Teh Kok How (IFAP DC COM WL SD)
> > > Sent: Wednesday, August 20, 2008 4:56 PM
> > > To: 'ltt-dev at lists.casi.polymtl.ca'
> > > Subject: Ltt-control-0.37, lttv-0.8.82: core.xml, line 0: invalid
> > > character, unrecognized token
> > >
> > > Hi;
> > > I have problems with ltt-control-0.37-09042007 &
> > > lttv-0.0.82-09042007. This is what I get from the CLI:
> > >
> > > [tehkok at linux2:~ 10]$ lttv -L /usr/local/lib/lttv/plugins -m
> > > batchAnalysis -s -m textDump -s -t /danube26_rootfs/trace Error in
> > > file /danube26_rootfs/trace/eventdefs/core.xml, line 0:
> > > invalid character, unrecognized token
> > > lttv.real: parser.c:123: error_callback: Assertion `0' failed.
> > > /usr/bin/lttv: line 15: 4369 Aborted $0.real $*
> > > [tehkok at linux2:~ 11]$
> > > [tehkok at linux2:~ 11]$ head /danube26_rootfs/trace/eventdefs/core.xml
> > > <?xml version="1.0"?>
> > > <facility name="core">
> > > <description>The core facility contains the basic tracing related
> > > events</description>
> > >
> > > <event name="facility_load">
> > > <description>Facility is loaded</description>
> > > <field name="name"><string/></field>
> > > <field name="checksum"><uint_fixed
> size="4"/></field>
> > > <field name="id"><uint_fixed size="4"/></field>
> > > <field name="int_size"><uint_fixed
> > > size="4"/></field> [tehkok at linux2:~ 12]$ [tehkok at linux2:~ 12]$ l
> > > /danube26_rootfs/trace/* -rwxr-xr-x 1 root root 27262976 Aug 19
> > > 23:40 /danube26_rootfs/trace/cpu_0 -rwxr-xr-x 1 root root 27262976
> > > Aug 19 23:40
> > > /danube26_rootfs/trace/cpu_1
> > > -rwxr-xr-x 1 root root 28311552 Aug 19 23:40
> > > /danube26_rootfs/trace/cpu_2
> > > -rwxr-xr-x 1 root root 27262976 Aug 19 23:40
> > > /danube26_rootfs/trace/cpu_3
> > >
> > > /danube26_rootfs/trace/control:
> > > total 3664
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 facilities_0
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 facilities_1
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 facilities_2
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 facilities_3
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 interrupts_0
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 interrupts_1
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 interrupts_2
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 interrupts_3
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 modules_0
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 modules_1
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 modules_2
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 modules_3
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 network_0
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 network_1
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 network_2
> > > -rwxr-xr-x 1 root root 65536 Aug 19 23:40 network_3
> > > -rwxr-xr-x 1 root root 1048576 Aug 19 23:40 processes_0 -rwxr-xr-x 1
>
> > > root root 1048576 Aug 19 23:40 processes_1 -rwxr-xr-x 1 root root
> > > 262144 Aug 19 23:40 processes_2 -rwxr-xr-x 1 root root 262144 Aug
> > > 19 23:40 processes_3
> > >
> > > /danube26_rootfs/trace/eventdefs:
> > > total 232
> > > -rw-r--r-- 1 root root 1596 Aug 19 23:40 compact.xml
> > > -rw-r--r-- 1 root root 1984 Aug 19 23:40 core.xml
> > > -rw-r--r-- 1 root root 5356 Aug 19 23:40 fs.xml
> > > -rw-r--r-- 1 root root 12152 Aug 19 23:40 kernel.xml
> > > -rw-r--r-- 1 root root 15820 Aug 19 23:40 kernel_arch_arm.xml
> > > -rw-r--r-- 1 root root 27183 Aug 19 23:40 kernel_arch_c2.xml
> > > -rw-r--r-- 1 root root 14292 Aug 19 23:40 kernel_arch_i386.xml
> > > -rw-r--r-- 1 root root 41195 Aug 19 23:40 kernel_arch_mips.xml
> > > -rw-r--r-- 1 root root 13657 Aug 19 23:40 kernel_arch_powerpc.xml
> > > -rw-r--r-- 1 root root 13649 Aug 19 23:40 kernel_arch_ppc.xml
> > > -rw-r--r-- 1 root root 30395 Aug 19 23:40 kernel_arch_x86_64.xml
> > > -rw-r--r-- 1 root root 5277 Aug 19 23:40 list.xml
> > > -rw-r--r-- 1 root root 1606 Aug 19 23:40 locking.xml
> > > -rw-r--r-- 1 root root 1909 Aug 19 23:40 mm.xml
> > > -rw-r--r-- 1 root root 3363 Aug 19 23:40 net.xml
> > > -rw-r--r-- 1 root root 1606 Aug 19 23:40 stack_arch_i386.xml
> > > -rw-r--r-- 1 root root 2240 Aug 19 23:40 stack_arch_x86_64.xml
> > > -rw-r--r-- 1 root root 1266 Aug 19 23:40 user_generic.xml
> > > -rw-r--r-- 1 root root 1259 Aug 19 23:40 xen.xml [tehkok at linux2:~
> > > 13]$
> > >
> > > Please advise. Thanks.
> > >
> > > Regards,
> > > Kok How
> >
> > _______________________________________________
> > ltt-dev mailing list
> > ltt-dev at lists.casi.polymtl.ca
> > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> >
>
> --
> Mathieu Desnoyers
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE
> 9A68
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
More information about the lttng-dev
mailing list