X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;ds=sidebyside;f=doc%2Fman%2Flttng-ust.3;h=818ef103ae407498c133ba9e64580595f3b47254;hb=94c9c48da8ea6424c01d17409cc6788f7ea70450;hp=3ba5c7cc8e46b2a554957d1fd7b5a99b488925b9;hpb=9b6435afbb89e2345ac7399620549db3e58f3f75;p=lttng-ust.git

diff --git a/doc/man/lttng-ust.3 b/doc/man/lttng-ust.3
index 3ba5c7cc..818ef103 100644
--- a/doc/man/lttng-ust.3
+++ b/doc/man/lttng-ust.3
@@ -257,7 +257,7 @@ carefully:
     - 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 "\-lllttng-ust".
+      library with "\-llttng-ust".
     - Include the tracepoint provider header into all C files using
       the provider.
     - Example:
@@ -287,9 +287,55 @@ carefully:
     application using "\-llibname" or loaded with LD_PRELOAD.
   - Enable instrumentation and control tracing with the "lttng" command
     from lttng-tools. See lttng-tools doc/quickstart.txt.
+  - Note for C++ support: although an application instrumented with
+    tracepoints can be compiled with g++, tracepoint probes should be
+    compiled with gcc (only tested with gcc so far).
 
 .fi
 
+.SH "USING LTTNG UST WITH DAEMONS"
+
+.nf
+Some extra care is needed when using liblttng-ust with daemon
+applications that call fork(), clone(), or BSD rfork() without a
+following exec() family system call. The library "liblttng-ust-fork.so"
+needs to be preloaded for the application (launch with e.g.
+LD_PRELOAD=liblttng-ust-fork.so appname).
+
+.fi
+
+.SH "CONTEXT"
+
+.PP
+Context information can be prepended by the tracer before each, or some,
+events. The following context information is supported by LTTng-UST:
+.PP
+
+.PP
+.IP "vtid"
+Virtual thread ID: thread ID as seen from the point of view of the
+process namespace.
+.PP
+
+.PP
+.IP "vpid"
+Virtual process ID: process ID as seen from the point of view of the
+process namespace.
+.PP
+
+.PP
+.IP "procname"
+Thread name, as set by exec() or prctl(). It is recommended that
+programs set their thread name with prctl() before hitting the first
+tracepoint for that thread.
+.PP
+
+.PP
+.IP "pthread_id"
+Pthread identifier. Can be used on architectures where pthread_t maps
+nicely to an unsigned long type.
+.PP
+
 .SH "ENVIRONMENT VARIABLES"
 
 .PP