From: alexandre.montplaisir@polymtl.ca (Alexandre Montplaisir)
Subject: [ltt-dev] no metadata tracefile
Date: Thu, 15 Sep 2011 09:31:35 -0400 [thread overview]
Message-ID: <4E71FE37.5040506@polymtl.ca> (raw)
In-Reply-To: <BC65C03AE25C1D4596B4AD414367C10F04BADF5D@AMSACEX2.americas.ad.flextronics.com>
Hi again,
On 11-09-14 02:05 PM, Ji Zhai wrote:
> 7. I used LTTV(0.12.36) to review the results:
>
> lttv -m textDump -t mcb00-main-aaillax-20110914130558687771830
>
> ** (process:20623): WARNING **: Trace /nas/jizhai/LTTng/mytrace/mcb00-main-aaillax-20110914130558687771830 has no metadata tracefile
>
> ** (process:20623): CRITICAL **: cannot open trace mcb00-main-aaillax-20110914130558687771830
> /home/jizhai/MyLocal/LTTng/bin/lttv: line 15: 20623 Segmentation fault $0.real $*
This happens if you don't pass the right directory to "lttv -t". You
have to give it the one containing the metadata_* and ust_* files directly.
However from your tarball, your metadata_0 and ust_0 files are in
different subdirectories. Is this what you obtained from a single
invocation of usttrace? If so then it means your different channels end
up in separate traces, and this is definitely not normal behavior.
If you put both ust_0 and metadata_0 files in the same directory, and
open that directory with LTTv, what do you get? I couldn't open it from
here, but I think it has to do with different endianness.
Cheers,
--
Alexandre Montplaisir
DORSAL lab,
?cole Polytechnique de Montr?al
next prev parent reply other threads:[~2011-09-15 13:31 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 [this message]
2011-09-15 15:03 ` Ji Zhai
2011-09-15 16:21 ` Alexandre Montplaisir
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=4E71FE37.5040506@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