Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: alexandre.montplaisir@polymtl.ca (Alexandre Montplaisir)
Subject: [ltt-dev] no metadata tracefile
Date: Thu, 15 Sep 2011 12:21:21 -0400	[thread overview]
Message-ID: <4E722601.7000603@polymtl.ca> (raw)
In-Reply-To: <BC65C03AE25C1D4596B4AD414367C10F04BAE255@AMSACEX2.americas.ad.flextronics.com>

On 11-09-15 11:03 AM, Ji Zhai wrote:
> Hi Alexandre,
>
> I got the metadata_0 and ust_0, which are in different directories, from a single invocation of usttrace. After copying metadata_0 and ust_0 into same directory, I used LTTV to open that directory and got the following error:
>
> lttv -m textDump -t 9341_5652200832964231168
>
> ** ERROR **: Undescribed event 1 in channel ust
> aborting...
> /home/jizhai/MyLocal/LTTng/bin/lttv: line 15: 14715 Aborted                 $0.real $* 
>
> As you mentioned, if there is endian problem, how to solve it?
> Thanks!
>

Are you able to compile LTTV on your target (you can use ./configure
--without-lttv-gui to compile without the GUI) and try to run it from
there? The trace reading library should be able to deal with
cross-endianness, but maybe you're hitting something else.

This is all I can think of at the moment. Anyone else has an idea?

The problem of different channels in different trace directories is
definitely a bug. All of the development effort is currently going
towards UST 2.0, which will offer much more robust session handling.
It'll definitely be worth retrying it with the new version.


Cheers,

-- 
Alexandre Montplaisir
DORSAL lab,
?cole Polytechnique de Montr?al





  reply	other threads:[~2011-09-15 16:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 20:47 Ji Zhai
2011-09-13 18:47 ` Ji Zhai
2011-09-13 18:47   ` Ji Zhai
2011-09-13 18:57   ` Mathieu Desnoyers
     [not found]   ` <BLU0-SMTP70493DBB789A80AE9E466A96050@phx.gbl>
2011-09-13 19:22     ` Ji Zhai
2011-09-13 20:03       ` Alexandre Montplaisir
2011-09-14 18:05         ` Ji Zhai
2011-09-14 18:05           ` Ji Zhai
2011-09-15 13:31           ` Alexandre Montplaisir
2011-09-15 15:03             ` Ji Zhai
2011-09-15 16:21               ` Alexandre Montplaisir [this message]
2011-09-15 16:21           ` Mathieu Desnoyers
     [not found]           ` <BLU0-SMTP10DC664C76B1F77D7B84BC96070@phx.gbl>
2011-09-15 19:27             ` Ji Zhai
2011-09-15 19:27               ` Ji Zhai
2011-09-18 22:23               ` Mathieu Desnoyers
     [not found]               ` <BLU0-SMTP44E853CF05E12EB77650D196080@phx.gbl>
2011-09-19 14:12                 ` Ji Zhai
2011-09-19 15:02                   ` Mathieu Desnoyers
     [not found]                   ` <BLU0-SMTP423756B62AF3BC179695E8960B0@phx.gbl>
2011-09-19 15:18                     ` Ji Zhai
2011-09-22 13:25                       ` Ji Zhai
2011-09-22 13:36                         ` Mathieu Desnoyers
2011-09-22 13:57                           ` Alex Luccisano (luccisa)
2011-09-22 15:12                             ` Mathieu Desnoyers
  -- strict thread matches above, loose matches on Subject: below --
2011-08-31 19:23 Ji Zhai

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=4E722601.7000603@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