X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=doc%2Fman%2Flttng-ust.3.txt;h=0593406a857a1ccf68cce4875239faa2c7fb3c25;hb=e09051727e07b47e43b4deffb986985fbb2c513d;hp=046e5b458233ed99574894ef7655c485f757fbcf;hpb=8902dadc26f8ed82bb77fc1c7fc4180631a92339;p=lttng-ust.git diff --git a/doc/man/lttng-ust.3.txt b/doc/man/lttng-ust.3.txt index 046e5b45..0593406a 100644 --- a/doc/man/lttng-ust.3.txt +++ b/doc/man/lttng-ust.3.txt @@ -738,6 +738,12 @@ without a following man:exec(3) family system call. The library application with the `LD_PRELOAD` environment variable (see man:ld.so(8)). +To use `liblttng-ust` with a daemon application which closes file +descriptors that were not opened by it, preload the `liblttng-ust-fd.so` +library before you start the application. Typical use cases include +daemons closing all file descriptors after man:fork(2), and buggy +applications doing ``double-closes''. + Context information ~~~~~~~~~~~~~~~~~~~ @@ -763,12 +769,16 @@ information about event filtering. reverse-lookup the source location that caused the event to be emitted. -+perf:thread:COUNTER+:: +`perf:thread:COUNTER`:: perf counter named 'COUNTER'. Use `lttng add-context --list` to list the available perf counters. + Only available on IA-32 and x86-64 architectures. +`perf:thread:raw:rN:NAME`:: + perf counter with raw ID 'N' and custom name 'NAME'. See + man:lttng-add-context(1) for more details. + `pthread_id`:: POSIX thread identifier. Can be used on architectures where `pthread_t` maps nicely to an `unsigned long` type. @@ -796,7 +806,9 @@ build IDs, and their debug link information are emitted as events by the tracer. The following LTTng-UST state dump events exist and must be enabled -to record application state dumps. +to record application state dumps. Note that, during the state dump +phase, LTTng-UST can also emit _shared library load/unload_ events +(see <> below). `lttng_ust_statedump:start`:: Emitted when the state dump begins. @@ -821,16 +833,26 @@ Fields: |Field name |Description |`baddr` -|Base address of loaded executable +|Base address of loaded executable. |`memsz` -|Size of loaded executable in memory +|Size of loaded executable in memory. |`path` -|Path to loaded executable file +|Path to loaded executable file. |`is_pic` -|Whether the executable is position-independent code +|Whether or not the executable is position-independent code. + +|`has_build_id` +|Whether or not the executable has a build ID. If this field is 1, you +can expect that an `lttng_ust_statedump:build_id` event record follows +this one (not necessarily immediately after). + +|`has_debug_link` +|Whether or not the executable has debug link information. If this field +is 1, you can expect that an `lttng_ust_statedump:debug_link` event +record follows this one (not necessarily immediately after). |=== `lttng_ust_statedump:build_id`:: @@ -846,10 +868,10 @@ Fields: |Field name |Description |`baddr` -|Base address of loaded library +|Base address of loaded library. |`build_id` -|Build ID +|Build ID. |=== `lttng_ust_statedump:debug_link`:: @@ -865,13 +887,107 @@ Fields: |Field name |Description |`baddr` -|Base address of loaded library +|Base address of loaded library. + +|`crc` +|Debug link file's CRC. + +|`filename` +|Debug link file name. +|=== + + +[[ust-lib]] +Shared library load/unload tracking +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +The <> and the LTTng-UST helper library +to instrument the dynamic linker (see man:liblttng-ust-dl(3)) can emit +**shared library load/unload tracking** events. + +The following shared library load/unload tracking events exist and must +be enabled to track the loading and unloading of shared libraries: + +`lttng_ust_lib:load`:: + Emitted when a shared library (shared object) is loaded. ++ +Fields: ++ +[options="header"] +|=== +|Field name |Description + +|`baddr` +|Base address of loaded library. + +|`memsz` +|Size of loaded library in memory. + +|`path` +|Path to loaded library file. + +|`has_build_id` +|Whether or not the library has a build ID. If this field is 1, you +can expect that an `lttng_ust_lib:build_id` event record follows +this one (not necessarily immediately after). + +|`has_debug_link` +|Whether or not the library has debug link information. If this field +is 1, you can expect that an `lttng_ust_lib:debug_link` event +record follows this one (not necessarily immediately after). +|=== + +`lttng_ust_lib:unload`:: + Emitted when a shared library (shared object) is unloaded. ++ +Fields: ++ +[options="header"] +|=== +|Field name |Description + +|`baddr` +|Base address of unloaded library. +|=== + +`lttng_ust_lib:build_id`:: + Emitted when a build ID is found in a loaded shared library (shared + object). See + https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html[Debugging Information in Separate Files] + for more information about build IDs. ++ +Fields: ++ +[options="header"] +|=== +|Field name |Description + +|`baddr` +|Base address of loaded library. + +|`build_id` +|Build ID. +|=== + +`lttng_ust_lib:debug_link`:: + Emitted when debug link information is found in a loaded + shared library (shared object). See + https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html[Debugging Information in Separate Files] + for more information about debug links. ++ +Fields: ++ +[options="header"] +|=== +|Field name |Description + +|`baddr` +|Base address of loaded library. |`crc` -|Debug link file's CRC +|Debug link file's CRC. |`filename` -|Debug link file name +|Debug link file name. |===