From: alexmonthy@voxpopuli.im (Alexandre Montplaisir)
Subject: [lttng-dev] LTTng project development activities November 2013
Date: Wed, 06 Nov 2013 17:37:19 -0500 [thread overview]
Message-ID: <527AC49F.6000200@voxpopuli.im> (raw)
In-Reply-To: <CAGDH53nLiu8CZnONuONSNz-c2+T0b2phBFx2H4wOZqAuZFHP6A@mail.gmail.com>
Thanks for the update Christian!
Allow me to give a small update on the TMF (Tracing and Monitoring
Framework, a.k.a. Eclipse trace viewer) front, most of which I did talk
about in my presentation at LinuxCon.
Recent features merged in git:
- Stand-alone RCP version!
This means it's now possible to download an architecture-dependant
build of the application that does not depend on Eclipse at all (only
needs a Java runtime). Users only interested in viewing traces, and not
in the whole Eclipse IDE integration, will probably prefer this version.
Builds are available at http://lttng.org/eclipse, and are updated
semi-regularly.
- Callstack View support for UST traces
Any UST trace taken with liblttng-ust-cyg-profile events will now
populate the Callstack View. This means you can now get the full
callstack for any application for which you have the source code!
Screenshot:
http://secretaire.dorsal.polymtl.ca/~alexmont/pics/callstackview.png
(The binary with debugging symbols is required to get the function names.)
- Trace synchronization infrastructure
The infrastructure is now in place to implement trace synchronization.
For example, synchronizing kernel traces from different machines, or for
synchronizing host+VM traces. Thanks to Benjamin Poirier, Masoume
Jabbarifar and Genevi?ve Bastien for their work on this feature!
- Index on disk
The viewer's index is now saved to disk, instead of being kept in
memory. This means reopening an already-indexed trace should now be much
faster.
A taste of things to come:
http://secretaire.dorsal.polymtl.ca/~alexmont/pics/TMF-teaser-oct-2013.png
- CPU usage view, based on kernel events
- Memory allocation graph, using malloc events from
liblttng-ust-libc-wrapper
- Support for dynamically-loaded libraries in the UST Callstack. With
function names all the way down!
next prev parent reply other threads:[~2013-11-06 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 22:19 Christian Babeux
2013-11-06 22:37 ` Alexandre Montplaisir [this message]
2013-11-06 23:17 ` Mathieu Desnoyers
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=527AC49F.6000200@voxpopuli.im \
--to=alexmonthy@voxpopuli.im \
/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