X-Git-Url: http://git.efficios.com/?a=blobdiff_plain;f=doc%2Fquickstart.txt;h=0cf44d69b0e45d6ae27cc516b85e17cd652574ce;hb=f88b0a988785de19db8a0d9ae22109bebc445b19;hp=abf61e76c1bac2081d30be0862ddd8fef4aded0c;hpb=90b9a26847f0eecba018f52e15f91bf992a23712;p=lttng-tools.git diff --git a/doc/quickstart.txt b/doc/quickstart.txt index abf61e76c..0cf44d69b 100644 --- a/doc/quickstart.txt +++ b/doc/quickstart.txt @@ -23,13 +23,13 @@ registry. To trace any instrumented applications or the kernel, a registered tracing session is needed beforehand. To interact with the session daemon and a tracing session, you should use the lttng command line UI (lttng). -Here is a list of some new powerful features the LTTng 2.0 kernel tracer -offers: +Here is a list of some powerful features the LTTng 2.0 kernel tracer offers: * Kprobes support * Function Tracer support * Context information support (add context data to an event) * Perf counter support + * Tracepoint support The next sections explain how to do tracing :) @@ -67,18 +67,18 @@ or enable ALL events (-a/--all): 3) Enable kprobes and/or the function tracer with lttng This is a new feature made possible by the new LTTng 2.0 kernel tracer. You can -enable a Kprobe (by Masami Hiramatsu) and data will be output in the trace -along side with your tracing data. +enable a dynamic probe and data will be output in the trace along side with +your tracing data. -# lttng enable-event aname --kprobe symbol+0xffff7260695 +# lttng enable-event aname --probe symbol+0xffff7260695 or -# lttng enable-event aname --kprobe 0xffff7260695 +# lttng enable-event aname --probe 0xffff7260695 -Either an
or a