Documentation: document that sequence len field is unsigned

[lttng-ust.git] / doc / man / lttng-gen-tp.1

diff --git a/doc/man/lttng-gen-tp.1 b/doc/man/lttng-gen-tp.1
index 551f003601b892fd77d45838814026eaf7e5d46d..84c05c9303ce1142716f8dc186413e07dcfed794 100644 (file)
--- a/doc/man/lttng-gen-tp.1
+++ b/doc/man/lttng-gen-tp.1
@@ -1,7 +1,7 @@
 .TH "LTTNG-GEN-TP" "1" "February 16, 2012" "" ""
 
 .SH "NAME"
-lttng-gen-tp \(em LTTng UST 2.0 tracepoint code generator
+lttng-gen-tp \(em LTTng UST 2.x tracepoint code generator
 
 .SH "SYNOPSIS"
 
@@ -29,7 +29,10 @@ link it with your application.
 Refer to the UST documentation for the
 advantages and disadvantage of each form.
 To compile the resulting .c file, you need to add the options
-"-llttng-ust -I."
+"\-llttng-ust \-I.".
+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).
 
 .SH "OPTIONS"
 
@@ -55,7 +58,7 @@ When no output is specified de default files are generated with the same base fi
 
 .SH "TEMPLATE FILE FORMAT"
 
-The template file, which has the usual extention \fB.tp\fP, contains a list of
+The template file, which has the usual extension \fB.tp\fP, contains a list of
 TRACEPOINT_EVENT definitions and other optional definition entries like
 TRACEPOINT_LOGLEVEL.
 (See lttng-ust(3) for the complete list of available definition.)