Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Gerald.Hansink@thomson.net (Hansink Gerald)
Subject: [ltt-dev] offline viewing of ltt trace files
Date: Mon, 27 Oct 2008 09:47:11 +0100	[thread overview]
Message-ID: <F9178F5F4473C94D921DE8E5C0D972163570CE@edgmsmail02.eu.thmulti.com> (raw)
Message-ID: <20081027084711.GEIjqjtAJmGUOAjZb2EFBeGfJs968eNG1mmKbM2t8nA@z> (raw)
In-Reply-To: <4903928C.70200@polymtl.ca>

Hi, 

It is possible now to read in the 'trace files' (I missed the eventdefs
dir because I did not do the 'lttctl -e' cmd and that initially did not
work because I did not had the 'facilities' dir on the target... but
this is fixed now :) ) 
But if I open the 'trace dir' I see in the 'statistics subwindow': 

Statistic for  '/media/usbdisk/trace' :

statistics summed :  1
cpu time :           8.667566508
events count :  242432
elapsed time (includes per process waiting time) :         310.733623650
cumulative cpu time (includes nested routines and modes) :
1.223022994

but the 'control flow view' subwindow does not show any lines (see
attachment). Do I need to do any additional actions to see the 'control
flow' of the trace I made? 
The trace is made with the probes: core, kernel, kernel_arch_mips

Best regards,
Gerald



-----Original Message-----
From: Pierre-Marc Fournier [mailto:pierre.marc.fournier@gmail.com] On
Behalf Of Pierre-Marc Fournier
Sent: zaterdag 25 oktober 2008 23:42
To: Hansink Gerald
Cc: ltt-dev at lists.casi.polymtl.ca
Subject: Re: [ltt-dev] offline viewing of ltt trace files

Hello,

You need to copy the whole trace directory. Once you are in the Add
Trace dialog, you must select the trace *directory*. If this doesn't
help, please explain what happens when it doesn't work.

No conversion is necessary.

pmf

Hansink Gerald wrote:
> Hi,
> 
>  
> 
> I have installed the following on the target:
> 
>  
> 
> LTTng 0.9.5
> 
> LTTcontrol 0.40
> 
>  
> 
> And on host LTTV 0.8.82
> 
>  
> 
> And I have copied the trace files to host to view them offline but if
I
> try to open these trace files by "Add trace" it won't succeed.
> 
> Do I have to convert the ltt trace files first? And using which tool?
> 
>  
> 
> Thanks.
> 
>  
> 
> Best regards,
> 
> Gerald
> 
>  
> 
> 
>
------------------------------------------------------------------------
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lttv.screen.png
Type: image/png
Size: 56216 bytes
Desc: lttv.screen.png
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20081027/91d34da7/attachment-0001.png>


  reply	other threads:[~2008-10-27  8:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 16:03 Hansink Gerald
2008-10-23 16:03 ` Hansink Gerald
2008-10-23 16:03 ` Hansink Gerald
2008-10-25 21:41 ` Pierre-Marc Fournier
2008-10-27  8:47   ` Hansink Gerald [this message]
2008-10-27  8:47     ` Hansink Gerald
2008-10-27  8:47     ` Hansink Gerald

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=F9178F5F4473C94D921DE8E5C0D972163570CE@edgmsmail02.eu.thmulti.com \
    --to=gerald.hansink@thomson.net \
    /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