From: Philippe Proulx Date: Thu, 27 Oct 2016 17:40:41 +0000 (-0400) Subject: Add legend for build scenario diagram symbols X-Git-Url: https://git.lttng.org./?a=commitdiff_plain;h=302407152eb1eaeb5088668556f76a3cc5398f8c;p=lttng-docs.git Add legend for build scenario diagram symbols Signed-off-by: Philippe Proulx --- diff --git a/2.7/images/export/ust-sit-symbols.png b/2.7/images/export/ust-sit-symbols.png new file mode 100644 index 0000000..9c85a28 Binary files /dev/null and b/2.7/images/export/ust-sit-symbols.png differ diff --git a/2.7/lttng-docs-2.7.txt b/2.7/lttng-docs-2.7.txt index 3210b83..e3cdd17 100644 --- a/2.7/lttng-docs-2.7.txt +++ b/2.7/lttng-docs-2.7.txt @@ -2543,7 +2543,7 @@ holding more than one tracepoint providers. Once you <>, you can use the `tracepoint()` macro in your application's source code to insert the tracepoints that this header -<> defines. +<>. The `tracepoint()` macro takes at least two parameters: the tracepoint provider name and the tracepoint name. The corresponding tracepoint @@ -2752,10 +2752,11 @@ In the following diagrams, we use the following file names: `libemon.so`:: User library shared object file. -The red star indicates that this object file is instrumented -(contains code which uses the `tracepoint()` macro). The spring -symbol between the application and a library means the application is -linked with the library at build time. +We use the following symbols in the diagrams of table below: + +[role="img-100"] +.Symbols used in the build scenario diagrams. +image::ust-sit-symbols.png[] We assume that path:{.} is part of the env:LD_LIBRARY_PATH environment variable in the following instructions. diff --git a/2.8/images/export/ust-sit-symbols.png b/2.8/images/export/ust-sit-symbols.png new file mode 100644 index 0000000..9c85a28 Binary files /dev/null and b/2.8/images/export/ust-sit-symbols.png differ diff --git a/2.8/lttng-docs-2.8.txt b/2.8/lttng-docs-2.8.txt index 79496e8..e72fc38 100644 --- a/2.8/lttng-docs-2.8.txt +++ b/2.8/lttng-docs-2.8.txt @@ -2628,7 +2628,7 @@ holding more than one tracepoint providers. Once you <>, you can use the `tracepoint()` macro in your application's source code to insert the tracepoints that this header -<> defines. +<>. The `tracepoint()` macro takes at least two parameters: the tracepoint provider name and the tracepoint name. The corresponding tracepoint @@ -2837,10 +2837,11 @@ In the following diagrams, we use the following file names: `libemon.so`:: User library shared object file. -The red star indicates that this object file is instrumented -(contains code which uses the `tracepoint()` macro). The spring -symbol between the application and a library means the application is -linked with the library at build time. +We use the following symbols in the diagrams of table below: + +[role="img-100"] +.Symbols used in the build scenario diagrams. +image::ust-sit-symbols.png[] We assume that path:{.} is part of the env:LD_LIBRARY_PATH environment variable in the following instructions.