From: "Kim, Seongab via lttng-dev" <lttng-dev@lists.lttng.org>
To: Philippe Proulx <eeppeliteloop@gmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [EXTERNAL] Re: babeltrace cannot open the trace but Trace Compass can open
Date: Thu, 23 Jul 2020 14:10:42 +0000 [thread overview]
Message-ID: <1b1cfdcc72fb4cbb8a81a1a0b13c6c15@HIMDWSMB06.ad.harman.com> (raw)
Message-ID: <20200723141042.fcPNW7bXX0R95-2aJeijA6EZCC8E2fBlBiSomBiwdeE@z> (raw)
In-Reply-To: <CAB4xu_1p0AYHhb1GASzOM9e-pdWmSkeTfZq2tQoyacso1MCUNA@mail.gmail.com>
Hello Phil,
> -----Original Message-----
> From: Philippe Proulx <eeppeliteloop@gmail.com>
> Sent: Thursday, July 23, 2020 4:00 PM
> To: Kim, Seongab <Seongab.Kim@harman.com>
> Cc: lttng-dev@lists.lttng.org
> Subject: Re: [EXTERNAL] Re: [lttng-dev] babeltrace cannot open the trace but
> Trace Compass can open
> > Here is the result.
> >
> > skim@d54030999178:~/ssd_work/traces$ babeltrace2 -o ctf-
> metadata ./kernel | grep -A10 '^clock {'
> > clock {
> > name = "monotonic";
> > uuid = "e00bcef2-1ef1-4f02-a241-8561834511fd";
> > description = "Monotonic Clock";
> > freq = 1000000000; /* Frequency, in Hz */
> > /* clock value offset from Epoch is: offset * (1/freq) */
> > offset = -48;
>
> Thanks, this is enough for us.
>
> When your account gets activated, could you copy this into the new issue's
> description?
>
> This way you can receive notifications when the issue gets updated.
>
FYI, I have created an issue, https://bugs.lttng.org/issues/1277.
Best regards,
Seongab
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-07-23 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 7:58 babeltrace cannot open the trace but Trace Compass can open Kim, Seongab via lttng-dev
2020-07-22 7:58 ` [lttng-dev] " Kim, Seongab via lttng-dev
2020-07-22 15:06 ` Philippe Proulx via lttng-dev
2020-07-22 15:06 ` [lttng-dev] " Philippe Proulx via lttng-dev
2020-07-23 9:08 ` [EXTERNAL] " Kim, Seongab via lttng-dev
2020-07-23 9:08 ` [lttng-dev] " Kim, Seongab via lttng-dev
2020-07-23 14:00 ` Philippe Proulx via lttng-dev
2020-07-23 14:00 ` [lttng-dev] " Philippe Proulx via lttng-dev
2020-07-23 14:03 ` Jonathan Rajotte-Julien via lttng-dev
2020-07-23 14:03 ` [lttng-dev] " Jonathan Rajotte-Julien via lttng-dev
2020-07-23 14:10 ` Kim, Seongab via lttng-dev [this message]
2020-07-23 14:10 ` Kim, Seongab via lttng-dev
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=1b1cfdcc72fb4cbb8a81a1a0b13c6c15@HIMDWSMB06.ad.harman.com \
--to=lttng-dev@lists.lttng.org \
--cc=Seongab.Kim@harman.com \
--cc=eeppeliteloop@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).