| 1 | .TH "LTTNG-UST-DL" "3" "December 19, 2013" "" "" |
| 2 | |
| 3 | .SH "NAME" |
| 4 | lttng-ust-dl \(em LTTng UST 2.x Dynamic Linker Tracing |
| 5 | |
| 6 | .SH "SYNOPSIS" |
| 7 | Launch your application with: |
| 8 | .TP |
| 9 | \fBLD_PRELOAD=liblttng-ust-dl.so\fP appname |
| 10 | .PP |
| 11 | This LD_PRELOAD library causes all calls to dlopen and dlclose in the |
| 12 | application to be traced with LTTng. The following two events need to be |
| 13 | enabled: ust_baddr:push and ust_baddr:pop. |
| 14 | |
| 15 | .SH "DESCRIPTION" |
| 16 | The events have the following detailed definitions: |
| 17 | .PP |
| 18 | .IP "ust_baddr:push" |
| 19 | This event is used to trace dlopen calls. The base address (where the dynamic |
| 20 | linker has placed the shared object) is recorded in the baddr-field. The path |
| 21 | to the shared object gets recorded in the sopath-field (as string). The file |
| 22 | size of the loaded object (in bytes) is recorded to the size-field and its time |
| 23 | of last modification (in seconds since Epoch) is recorded in the mtime-field. |
| 24 | .IP "ust_baddr:pop" |
| 25 | This event is used to trace dlclose calls. The base address of the shared |
| 26 | object that got closed is recorded in the baddr-field. |
| 27 | .PP |
| 28 | |
| 29 | .SH "SEE ALSO" |
| 30 | lttng-ust(3), dlopen(3), lttng(1) |
| 31 | .SH "BUGS" |
| 32 | If you encounter any issues or usability problem, please report it on |
| 33 | our mailing list <lttng-dev@lists.lttng.org> to help improve this |
| 34 | project. |
| 35 | .SH "CREDITS" |
| 36 | liblttng-ust is distributed under the GNU Lesser General Public License |
| 37 | version 2.1. The headers are distributed under the MIT license. |
| 38 | |
| 39 | See http://lttng.org for more information on the LTTng project. |
| 40 | |
| 41 | Mailing list for support and development: <lttng-dev@lists.lttng.org>. |
| 42 | |
| 43 | You can find us on IRC server irc.oftc.net (OFTC) in #lttng. |
| 44 | .SH "AUTHORS" |
| 45 | liblttng-ust was originally written by Mathieu Desnoyers, with additional |
| 46 | contributions from various other people. It is currently maintained by |
| 47 | Mathieu Desnoyers <mathieu.desnoyers@efficios.com>. |