X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=doc%2Fman%2Ftracelog.3.txt;h=1f97a0bdd68b092c4bfa7d93df49b7b1681b91c1;hb=e436e84d48332d559fe60c1a5eba81f03e9f38f9;hp=8997f1171fe081545333bdd1fc36d893b94fc3f0;hpb=1d41a8d75d789f60a0da6e1e4f06425cd8fe0b23;p=lttng-ust.git

diff --git a/doc/man/tracelog.3.txt b/doc/man/tracelog.3.txt
index 8997f117..1f97a0bd 100644
--- a/doc/man/tracelog.3.txt
+++ b/doc/man/tracelog.3.txt
@@ -15,37 +15,46 @@ SYNOPSIS
 
 [verse]
 #define *tracelog*('level', 'fmt', ...)
-#define *vtracelog*('level', 'fmt', 'va_list' ap)
+#define *vtracelog*('level', 'fmt', 'ap')
 
-Link with `-llttng-ust`.
+Link with `-llttng-ust -llttng-ust-common`.
 
 
 DESCRIPTION
 -----------
-The LTTng-UST `tracelog()` API allows you to trace your application with
-the help of a simple man:printf(3)-like macro, with an additional
-parameter for the desired log level. The 'fmt' argument is passed
-directly to the 'fmt' parameter of man:vasprintf(3), as well as
-the optional parameters following 'fmt'.
+The LTTng-UST `tracelog()` and `vtracelog()` API allows you to trace
+your application with the help of simple man:printf(3)-like and
+man:vprintf(3)-like macros, with an additional parameter for the desired
+log level.
 
-The purpose of `tracelog()` is to ease the migration from logging to
-tracing.
+The 'fmt' argument is passed directly as the 'fmt' parameter of
+man:vasprintf(3), as well as:
+
+For `tracelog()`::
+    The optional parameters following 'fmt'.
+
+For `vtracelog()`::
+    The 'ap' parameter as the 'ap' parameter of man:vasprintf(3)
+    (`va_list` type).
+
+The purpose of `tracelog()` and `vtracelog()` is to ease the migration
+from logging to tracing.
 
 The available values for the 'level' parameter are:
 
 include::log-levels.txt[]
 
-To use `tracelog()` or `vtracelog()`, include `<lttng/tracelog.h>` where you
-need it, and link your application with `liblttng-ust`.
-See the <<example,EXAMPLE>> section below for a complete usage example.
+To use `tracelog()` or `vtracelog()`, include `<lttng/tracelog.h>` where
+you need it, and link your application with `liblttng-ust`. See the
+<<example,EXAMPLE>> section below for a complete usage example.
 
-Once your application is instrumented with `tracelog()` calls and
-ready to run, use man:lttng-enable-event(1) to enable the
-`lttng_ust_tracelog:*` event. You can isolate specific log levels with
-the nloption:--loglevel and nloption:--loglevel-only options of this
-command.
+Once your application is instrumented with `tracelog()` and/or
+`vtracelog()` calls and ready to run, use man:lttng-enable-event(1) to
+enable the `lttng_ust_tracelog:*` event. You can isolate specific log
+levels with the nloption:--loglevel and nloption:--loglevel-only options
+of this command.
 
-The `tracelog()` events contain the following fields:
+The `tracelog()` and `vtracelog()` events contain the following fields:
 
 [options="header"]
 |===
@@ -64,8 +73,8 @@ The `tracelog()` events contain the following fields:
 |Formatted string output.
 |===
 
-If you do not need to attach a specific log level to a `tracelog()`
-call, use man:tracef(3) instead.
+If you do not need to attach a specific log level to a
+`tracelog()`/`vtracelog()` call, use man:tracef(3) instead.
 
 See also the <<limitations,LIMITATIONS>> section below for important
 limitations to consider when using `tracelog()` or `vtracelog()`.
@@ -106,7 +115,7 @@ like this:
 
 [role="term"]
 ----
-$ cc -o app app.c -llttng-ust
+$ cc -o app app.c -llttng-ust -llttng-ust-common
 ----
 
 You can create an LTTng tracing session, enable all the `tracelog()`
@@ -162,6 +171,7 @@ include::common-authors.txt[]
 SEE ALSO
 --------
 man:tracef(3),
+man:vtracef(3),
 man:lttng-ust(3),
 man:lttng(1),
 man:printf(3)