From: alexandre.montplaisir@polymtl.ca (Alexandre Montplaisir)
Subject: [lttng-dev] Viewing userspace apps traces
Date: Wed, 03 Oct 2012 23:41:53 -0400 [thread overview]
Message-ID: <506D0581.3030400@polymtl.ca> (raw)
In-Reply-To: <506BD225.3030906@fnac.net>
Sorry for the late reply, I had to update/rebase some of the stuff first...
(Cross-posting linuxtools-dev, as it might interest some people who
follow that list too. This is about extending TMF to implement a
graphical view for a specific UST trace type.)
On 12-10-03 01:50 AM, Paul Chavent wrote:
> [...]
>
> On 10/02/2012 10:29 PM, Alexandre Montplaisir wrote:
>> [...]
>>
>> 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!)
>
> I would like to see, eg, one line per tid, and on each line, the value
> of one context or argument value.
>
> I'm ready to follow an exercise for extending the framework !
Ok good! We don't have a nice tutorial ready yet, as most parts are
still working their way upstream. But if you want to dig into it and try
it out now, you can:
1 - Set up the development environment for TMF:
http://wiki.eclipse.org/Linux_Tools_Project/LTTng_Eclipse_Plug-in_Development_Environement_Setup
2 - Checkout the "lttng-kepler" branch in the git. This is where the
latest development happens.
3 - Apply those two patches, in that order:
https://git.eclipse.org/r/#/c/7747/
https://git.eclipse.org/r/#/c/7748/
(you can copy-paste the "cherry-pick" command shown on the page)
4 - Download the example program and view from:
git://git.dorsal.polymtl.ca/~alexmont/ust-example.git
Now at this point you should be able to import and build the example
plugins (ust.example.core and ust.example.ui) and the TMF/LTTng ones in
the same workspace.
You can try it to make sure it works correctly : take a UST trace of the
"myprog" program, and then load it into TMF, and show the "Example ->
Connections" view. It should display the yellow and green rectangles
corresponding to the states that were defined.
After that, it shouldn't be too hard (famous last words...) to rework
the ust.example.* code to fit your application. The points of interest
will be (before renames):
MyUstTraceInput, line 85+: This is where you assign your trace events to
states
ConnectionsPresentationProvider, line 31-34: This is where you assign
the colors to each state in the view
and same file, lines 64-68 and 81-85 : This is where you assign the
trace's states to the ones in the view.
(one place is for the actual colored rectangle, the other is for the
tooltips, iirc).
If you have any question or problem, please let me know!
Good luck ;)
--
Alexandre Montplaisir
DORSAL lab,
?cole Polytechnique de Montr?al
next prev parent reply other threads:[~2012-10-04 3:41 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
2012-10-03 5:50 ` Paul Chavent
2012-10-04 3:41 ` Alexandre Montplaisir [this message]
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=506D0581.3030400@polymtl.ca \
--to=alexandre.montplaisir@polymtl.ca \
/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