Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: alexandre.montplaisir@polymtl.ca (Alexandre Montplaisir)
Subject: [ltt-dev] RFC LTTv TextDump
Date: Mon, 22 Nov 2010 15:52:25 -0500	[thread overview]
Message-ID: <4CEAD809.4020205@polymtl.ca> (raw)
In-Reply-To: <4CEAD092.8020604@polymtl.ca>

On 10-11-22 03:20 PM, David Goulet wrote:
> Hi everyone,
>
> I propose here, only an idea, to create a lttv plugin for "human 
> readable" text dump. There is too much information in the current 
> textdump and it's not quite useful showing a lot of cryptic symbol and 
> sec.nsec timestamp.
> ...

Make the textdump readable? What is this heresy!

But seriously, +1 from me too. Especially for the long path that gets 
repeated every line, we could only put it once at the start of the file.
For kernel traces, the PID, TGID and exec name are nice to have, but 
that's it. May need to add a "cpu number" that's normally at the end of 
the file path.

Not sure about making the timestamp in H:M:S format though. This should 
be the job of the viewer, as it would make parsing more difficult. 
Unless we want two different modules, a "human readable textdump" and a 
"parseable textdump".


Cheers,
Alexandre





  reply	other threads:[~2010-11-22 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 20:20 David Goulet
2010-11-22 20:52 ` Alexandre Montplaisir [this message]
2010-11-23 18:26 ` Mathieu Desnoyers
2010-11-23 19:38   ` Alexandre Montplaisir
2010-11-23 20:15     ` Mathieu Desnoyers
2010-11-24 19:11     ` Michel Dagenais
2010-11-24 20:43       ` David Goulet
2010-11-24 22:49         ` Julien Desfossez

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=4CEAD809.4020205@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