From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: ltt-dev@shafik.org, linux-kernel@vger.kernel.org
Subject: LTTng 0.10 for kernel 2.6.26
Date: Mon, 14 Jul 2008 20:12:02 -0400 [thread overview]
Message-ID: <20080715001202.GA21184@Krystal> (raw)
Hi,
I just released LTTng kernel tracer 0.10 for kernel 2.6.26. The new
userspace markers now have a brand new package, which includes the
linker script for x86 32 and 64 bits and example code and Makefile,
available at :
http://ltt.polymtl.ca/packages/markers-userspace-0.5.tar.bz2
As always, the kernel patches are available at :
http://ltt.polymtl.ca/lttng/patch-2.6.26-0.10.tar.bz2
The userspace tracing control tool :
http://ltt.polymtl.ca/lttng/ltt-control-0.49-14072008.tar.gz
The trace viewer :
http://ltt.polymtl.ca/packages/lttv-0.10.0-pre13-27052008.tar.gz
There is currently limited userspace tracing support :
- It traces through a system call
- It records a string taken from the syscall parameter to the kernel
event "userspace_string". It's not as compact as the kernel binary
format, but it "does the job" for now. Other type support are WIP.
- The markers userspace object, linked with the binary, adds a section
to describe the markers and new constructors/destructors to register
the markers to the kernel.
- It supports instrumentation of libraries and executables.
- It is currently limited to activation of system-wide tracepoints. The
easiest way to activate them is to have them registered when
ltt-armalluser is executed. It will automatically find them through
/proc and enable them system-wide. They will then be automatically
activated for all new processes created which register these markers.
- It is better to tell yourself to /proc/ltt to activate the named
markers if you plan to run a program which has a short execution time,
because they would have to be enabled before they are listed in /proc.
See the ltt-armalluser script as an example; just put your own marker
name instead.
Feedback is welcome.
See the version compatibility list for details :
http://ltt.polymtl.ca/svn/ltt/branches/poly/doc/developer/lttng-lttv-compatibility.html
And follow the quickstart guide for instructions about how to install
and use the tools.
http://ltt.polymtl.ca/svn/ltt/branches/poly/QUICKSTART
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
reply other threads:[~2008-07-15 0:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080715001202.GA21184@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox