From: stefanha@gmail.com (Stefan Hajnoczi)
Subject: [lttng-dev] Automatic instrumentation using a clang plugin
Date: Thu, 12 Apr 2012 10:10:22 +0100 [thread overview]
Message-ID: <CAJSP0QWJUq3pA_kUPnXK1riRUHDh5nYg4Rj=QhbNFLsLbbpiQw@mail.gmail.com> (raw)
You may have already seen this, it's a userspace C/C++ tracing tool
that uses a clang plugin to instrument all functions in the source
code including arguments and type information. This allows it to
easily trace everything that happens inside an app.
The actual tracer is probably along the lines of LTTng UST, I haven't
checked. Here's the link to the clang plugin which I think is the
interesting part:
https://github.com/yotamr/traces/tree/master/trace_instrumentor
and the wrapper script to use in place of gcc/g++:
https://github.com/yotamr/traces/blob/master/ccwrap.py
Hope this is not too spammy for the list, just wanted to share because
the clang plugin is an interesting approach. The advantage is that
you don't need to hope your trace points provide the right information
- you can trace any function. Another approach to achieving similar
ease-of-use would be a dynamic userspace probing mechanism that uses
DWARF info but I'm not sure if the right information is available in
the DWARF info or how hard dynamic probing is in practice.
Stefan
reply other threads:[~2012-04-12 9:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJSP0QWJUq3pA_kUPnXK1riRUHDh5nYg4Rj=QhbNFLsLbbpiQw@mail.gmail.com' \
--to=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox