[lttng-dev] Lttng user application tracing
jeremie.galarneau at efficios.com
Tue May 5 19:32:42 EDT 2015
On Tue, May 5, 2015 at 12:55 PM, Beatriz Aguilar <beatriz.aguilar at bsc.es>
> I am trying to trace a user application with Lttng.
> I would like to know if it is possible to do it without introducing
> tracepoints in the user code like when the kernel is traced.
> For example, I would like to see what every CPU/process is doing in an MPI
> + OpenMP application without putting tracepoints in it.
Without instrumenting your application, you will be limited to the
information provided by the kernel instrumentation which includes syscalls.
Those can already provide you with quite a bit of information to understand
what an application is doing.
Moreover, you can use a couple of lttng-ust helper libraries to trace calls
to some libc functions . You could probably develop other helpers based
around the same idea (overloading symbols) to trace MPI and OpenMP calls
Unfortunately, if you really want to instrument your application's
internals, you will have to manually add tracepoints to the code. Dynamic
tracing, which we don't support yet, would let you insert probes at runtime
without the need for this static instrumentation.
> Is that possible or is there any alternative to Lttng to generate ctf
> Thank you very much.
> Your help is very much appreciated =)
> Beatriz Aguilar
> WARNING / LEGAL TEXT: This message is intended only for the use of the
> individual or entity to which it is addressed and may contain
> information which is privileged, confidential, proprietary, or exempt
> from disclosure under applicable law. If you are not the intended
> recipient or the person responsible for delivering the message to the
> intended recipient, you are strictly prohibited from disclosing,
> distributing, copying, or in any way using this message. If you have
> received this communication in error, please notify the sender and
> destroy and delete any copies you may have received.
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lttng-dev