From: alexmonthy@voxpopuli.im (Alexandre Montplaisir)
Subject: [lttng-dev] Viewing userspace apps traces
Date: Tue, 02 Oct 2012 16:29:24 -0400 [thread overview]
Message-ID: <506B4EA4.8050407@voxpopuli.im> (raw)
In-Reply-To: <506B4A21.6080309@fnac.net>
Hi Paul,
On 12-10-02 04:10 PM, Paul Chavent wrote:
> Hi.
>
> Today, I've tested the tracing of a user space app.
>
> I wonder what is the best solution for viewing it ?
>
> I have tried babeltrace that produce a good comprehensive text outpout.
> I have tried eclipse that isn't able to use the vtid and vpid context.
> It's unfortunate as i would like to see a timeline representation...
Do you mean the Events view does not show the event contexts? It should,
afaik. It could be a bug.
As for graphical views, like timegraphs, it's not easy to have a general
view that can work with any UST trace. Each application defines its own
event types, so we have no guarantee for any given event type to be there.
What would you like see in your "timeline representation" exactly? Maybe
we could give you some pointers as to how to implement such a view.
(We're currently working on making it easy to extend the framework to
implement new views, so this could be a good exercise!)
> Is it a good solution to use the custom text parser of the eclipse tool ?
Not really, the custom parsers are, for example, when you have a text
log and want to import it into the TMF framework. LTTng/UST traces are
in CTF format, and that format is already supported in TMF.
Cheers,
--
Alexandre Montplaisir
DORSAL lab,
?cole Polytechnique de Montr?al
next prev parent reply other threads:[~2012-10-02 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 20:10 Paul Chavent
2012-10-02 20:29 ` Alexandre Montplaisir [this message]
2012-10-03 5:50 ` Paul Chavent
2012-10-04 3:41 ` Alexandre Montplaisir
2012-10-04 13:40 ` eamcs/eedbhu
2012-10-04 20:39 ` Paul Chavent
2012-10-05 12:15 ` Bernd Hufmann
2012-10-05 19:29 ` Paul Chavent
2012-10-04 10:56 ` Oestman, Fredrik
2012-10-04 14:29 ` 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=506B4EA4.8050407@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