3) Link your program against liblttng-ust.so.
-4) Enable the UST debug loglevel when tracing with the following
- sequence of commands from lttng-tools:
+4) Enable UST events when tracing with the following sequence of commands
+ from lttng-tools:
lttng create
- lttng enable-event -u -a --loglevel=TRACE_DEBUG
+ lttng enable-event -u -a
lttng start
[... run your program ...]
lttng stop
sample_component,
/*
- * tracepoint name, same format as sample provider. Does not
- * need to be declared before. in this case the name is
- * "message"
+ * tracepoint name, characters permitted follow the same
+ * constraints as the provider name. The name of this example
+ * event is "sample_event".
*/
- message,
+ sample_event,
/*
* TP_ARGS macro contains the arguments passed for the tracepoint
debug information with line-level scope (TRACEPOINT_EVENT default)
TRACE_DEBUG 14
- debug-level message (trace_printf default)
+ debug-level message
See lttng(1) for information on how to use LTTng-UST loglevels.
nicely to an unsigned long type.
.PP
-.SH "BASE ADDRESS STATEDUMP (Experimental feature)"
+.SH "BASE ADDRESS STATEDUMP"
.PP
-Warning: This is an experimental feature known to cause deadlocks when the
-traced application uses fork, clone or daemon. Only use it for debugging and
-testing. Do NOT use it in production.
-
If an application that uses liblttng-ust.so becomes part of a session,
information about its currently loaded shared objects will be traced to the
session at session-enable time. To record this information, the following event
recommended for applications with time constraints on the process
startup time.
.PP
-.IP "LTTNG_UST_WITH_EXPERIMENTAL_BADDR_STATEDUMP"
-Experimentally allow liblttng-ust to perform a base-address statedump on session-enable.
+.IP "LTTNG_UST_WITHOUT_BADDR_STATEDUMP"
+Prevent liblttng-ust to perform a base-address statedump on session-enable.
.PP
.SH "SEE ALSO"