application: either statically or dynamically. Please follow
carefully:
- 1.1) Compile the Tracepoint provider with the application, either
- directly or through a static library (.a):
- - Into exactly one object of your application: define
+ 1) Compile the Tracepoint Provider with the application, either
+ directly or through a static library (.a):
+ - Into exactly one object of your application, define
"TRACEPOINT_DEFINE" and include the tracepoint provider.
- Use "\-I." for the compilation unit containing the tracepoint
- provider include (e.g. tp.c).
- - Link application with "\-ldl".
- - If building the provider directly into the application,
- link the application with "\-llttng-ust".
- - If building a static library for the provider, link the static
- library with "\-llttng-ust".
+ provider include (e.g., tp.c).
+ - Link the application with "\-llttng-ust" and "\-ldl".
- Include the tracepoint provider header into all C files using
the provider.
- Examples:
nicely to an unsigned long type.
.PP
-.SH "BASE ADDRESS STATEDUMP"
+.SH "BASE ADDRESS STATEDUMP (Experimental feature)"
.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_WITHOUT_BADDR_STATEDUMP"
-Prevent liblttng-ust to perform a base-address statedump on session-enable.
+.IP "LTTNG_UST_WITH_EXPERIMENTAL_BADDR_STATEDUMP"
+Experimentally allow liblttng-ust to perform a base-address statedump on session-enable.
.PP
.SH "SEE ALSO"