2 This package contains the trace reading library and trace viewing tools for
3 the new Linux Trace Toolkit trace format. The associated kernel files to
4 generate the new traces are not yet included. In the meantime, a converter
5 from the old trace format to the new is provided. For more detailed information
6 see doc/developer/index.html
12 Some development libraries are needed for compiling :
14 gtk 2 development libraries (libgtk2.0, libgtk2.0-dev)
15 glib 2 development libraries (libglib2.0-0, libglib2.0-dev)
16 libpopt development libraries (libpopt0, libpopt-dev)
17 libpango development libraries (libpango1.0, libpango1.0-dev)
19 To compile the source tree from a tarball, simply follow these steps :
25 After running ./configure, you can also go in specific subdirectories and
26 use make, make install.
33 - Run ./lttv -m guievents -m guicontrolflow -m guievents -t path_to_trace
36 * Source Tree Structure
38 This is a sample of the suggested tree for Linux Trace Toolkit.
40 ltt: new trace format reading library (and converter).
42 debian: debian config files (currently empty).
44 doc/user: User related documentation.
45 doc/developer: Developer related documentation.
46 kernel: Linux Trace Toolkit kernel code (currently empty).
47 lttd: Linux Trace Toolkit daemon (currently empty).
48 lttv: Linux Trace Toolkit trace analysis tool and viewer.
49 lttv/modules: Linux Trace Toolkit analysis tool and viewer plugin modules.
50 specs: RPM config files (currently empty).
53 * The rest of the tools
55 You must use the lastest versions of patches for the Linux Kernel. That includes
56 relayfs and ltt patches, available on the ltt-dev mailing list at
57 http://www.listserv.shafik.org/pipermail/ltt-dev/. You will find there the
58 lastest version of the trace daemon that must be used to create the traces. (in
59 the TraceToolkit package)
61 Once your traces are created, you must use the convert tool to create a trace in
62 the proper format from them.
67 This source tree is based on the autotools suite from GNU to simplify
68 portability. Here are some things you should have on your system in order to
69 compile the subversion repository tree :
72 GNU autotools (automake-1,7, autoconf2.50, autoheader2.50)
73 (make sure your system wide "automake" points to version 1.7!)
75 (for more information, go to http://www.gnu.org/software/autoconf/)
77 If you get the tree from the repository, you will need to use the autogen.sh
78 script. It calls all the GNU tools needed to prepare the tree configuration.