X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=LTTngManual.html;h=780e5483a6b19ef66da4dfc1722d73067ed32fd8;hb=db44dd151688cbe0eea2062ad9ea96982a1bba2d;hp=58bb9ae1357da6cbb9992a08d250446a54a58626;hpb=b6d6974fffb55d69e779bff399a6d1fe9a513676;p=lttv.git diff --git a/LTTngManual.html b/LTTngManual.html index 58bb9ae1..780e5483 100644 --- a/LTTngManual.html +++ b/LTTngManual.html @@ -8,7 +8,7 @@
+The Eclipse LTTng trace analysis tool is released under the EPL and uses the +LTTV trace reading library (LGPLv2.1). +
The UST (Userspace Tracing) and the Userspace RCU libraries are released under the LGPLv2.1 license, which allows linking with non-GPL (BSD, proprietary...) applications. The associated headers are released under MIT-style/BSD-style @@ -171,7 +174,7 @@ gtk 2.4 or better development libraries (Fedora : gtk2, gtk2-devel) note : For Fedora users : this might require at least core 3 from Fedora, or you might have to compile your own GTK2 library. -glib 2.4 or better development libraries +glib 2.16 or better development libraries (Debian : libglib2.0-0, libglib2.0-dev) (Fedora : glib2, glib2-devel) libpopt development libraries @@ -191,8 +194,7 @@ libc6 development librairies
See the list of compatibilities between LTTng, ltt-control and LTTV at : LTTng+LTTV -versions compatibility. +href="http://lttng.org/cgi-bin/gitweb.cgi?p=lttv.git;a=blob_plain;f=doc/developer/lttng-lttv-compatibility.html;hb=HEAD">LTTng+LTTV versions compatibility.
+su - +cd /usr/src/lttng/lttng-modules-0.x +KERNELDIR=/usr/src/linux-2.6.X-lttng-0.x.xx make +KERNELDIR=/usr/src/linux-2.6.X-lttng-0.x.xx make modules_install ++
su - cd /usr/src -wget http://ltt.polymtl.ca/lttng/ltt-control-0.x-xxxx2006.tar.gz +wget http://lttng.org/files/lttng/ltt-control-0.x-xxxx2006.tar.gz gzip -cd ltt-control-0.x-xxxx2008.tar.gz | tar xvof - cd ltt-control-0.x-xxxx2006 (refer to README to see the development libraries that must be installed on you @@ -382,12 +384,12 @@ ldconfigMake sure you selected the kernel menuconfig option : -or <*> Support logging events from userspace + <M> or <*> Support logging events from userspace And that the ltt-userspace-event kernel module is loaded if selected as a module. Simple userspace tracing is available through -echo "some text to record" > /mnt/debugfs/ltt/write_event +echo "some text to record" > /mnt/debugfs/ltt/write_event It will appear in the trace under event : channel : userspace @@ -401,7 +403,7 @@ or different from the visualisation machine) su - cd /usr/src -wget http://ltt.polymtl.ca/packages/lttv-0.x.xx-xxxx2008.tar.gz +wget http://lttng.org/files/packages/lttv-0.x.xx-xxxx2008.tar.gz gzip -cd lttv-0.x.xx-xxxx2008.tar.gz | tar xvof - cd lttv-0.x.xx-xxxx2008 (refer to README to see the development libraries that must be installed on your @@ -540,18 +542,16 @@ for LTTng probe examples.Adding userspace instrumentation
Add new events to userspace programs with -userspace markers packages. +userspace markers packages. Get the latest markers-userspace-*.tar.bz2 and see the Makefile and examples. It allows inserting markers in executables and libraries, currently only on x86_32 and x86_64. See markers-userspace-0.5.tar.bz2 or more recent. +href="http://lttng.org/files/packages/markers-userspace-0.5.tar.bz2">markers-userspace-0.5.tar.bz2 or more recent.-Note that a new design document for a 3rd generation of tracepoint/marker-based -userspace tracing is available at LTTng User-space Tracing -Design. This new infrastructure is not yet implemented. +Note that tracepoint/marker-based userspace tracing is available at LTTng User-space Tracer (UST).
The easy quick-and-dirty way to perform userspace tracing is currently to write