Linux Trace Toolkit

Linux Trace Toolkit Downloads

This is the stable version: TraceToolkit-0.9.5a.tgz

The layout of the package is as follows (starting from the TraceToolkit-x.y.z directory) :

COPYPING
The GNU GPL License.
Help/
LTT's help files as found in the documentation section of this web page.
Daemon/
The directory containing the trace daemon.
Examples/
Example code for using the custom event creation code in user-space or in kernel-space.
LibLTT/
The event database library to read and browse event traces.
LibUserTrace/
The user-space library for tracing user-space events.
Patches/
The directory containing the different patches.
Visualizer/
The directory containing the trace toolkit front-end.
README
The readme file discussing the content of the LTT package
"the rest"
Most other files in the package's root directory are required for autoconf/autobuild.

More details are given in the documentation section about the installation of LTT and the different script files.

Old stable versions :
   0.9.4
   0.9.3
   0.9.2
   0.9.1
   0.9.0

Development versions :
pre-0.9.6 series:
   0.9.6pre4
   0.9.6pre3
   0.9.6pre2
   0.9.6pre1

pre-0.9.5 series:
   0.9.5pre6
   0.9.5pre5
   0.9.5pre4
   0.9.5pre3
   0.9.5pre2
   0.9.5pre1

pre-0.9.4 series:
   0.9.4pre4
   0.9.4pre3
   0.9.4pre2

Pre-compiled 2.2.14 kernel with trace patch for LTT 0.9.3 :
   bzImage_trace
   modules.tgz
   .config

I assume you know how to use lilo. The ".config" was used to compile the given kernel.

Sample trace files:
These sample trace files are readable with LTT 0.9.3 only.
out301.tgz: A trace of processes using the LXRT subsystem of RTAI. This is a fairly complex trace.
out302.tgz: A trace of a command-line Linux with a couple of commands issued such as 'dir', 'ps' and 'man'. This is fairly simple.

This is in case you don't feel playing around with kernel patching, lilo, modules, devices, daemons, etc. but still want to see the front-end in action. Each of these archives contains 2 files, a ".trace" file and a ".proc" file. Both are needed to view a trace graphically. More information can be found in the documentation section.