From: Philippe Proulx via lttng-dev <lttng-dev@lists.lttng.org> To: "Kim, Seongab" <Seongab.Kim@harman.com> Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org> Subject: Re: [EXTERNAL] Re: babeltrace cannot open the trace but Trace Compass can open Date: Thu, 23 Jul 2020 10:00:29 -0400 [thread overview] Message-ID: <CAB4xu_1p0AYHhb1GASzOM9e-pdWmSkeTfZq2tQoyacso1MCUNA@mail.gmail.com> (raw) In-Reply-To: <7cb6526a78a9468e969a0fe36f42c6d7@HIMDWSMB06.ad.harman.com> On Thu, Jul 23, 2020 at 5:09 AM Kim, Seongab <Seongab.Kim@harman.com> wrote: > > Hello Phil, > > > -----Original Message----- > > From: Philippe Proulx <eeppeliteloop@gmail.com> > > Sent: Wednesday, July 22, 2020 5:06 PM > > To: Kim, Seongab <Seongab.Kim@harman.com> > > Cc: lttng-dev@lists.lttng.org > > Subject: [EXTERNAL] Re: [lttng-dev] babeltrace cannot open the trace but > > Trace Compass can open > > > > Thank you for the bug report. > > > > Can I kindly ask you to create an official issue for this? > > > > Go to > > <https://clicktime.symantec.com/38qgEsYhBTfCNnYpLPoAn647Vc?u=https% > > 3A%2F%2Fbugs.lttng.org%2Fprojects%2Fbabeltrace%2Fissues%2Fnew>. > > > > I'd also like you to attach the offending CTF trace so that I can analyze it if it > > doesn't contain sensitive data and is somewhat small. > > I created an account in Redmine, but I'm still waiting for the account activation mail. I tried to click the resend mail link two times without success. > Also the trace is big (1.4 GB) and it contains sensitive data. > > > If it's not possible, do: > > > > $ babeltrace2 -o ctf-metadata /mnt/ssd/work/skim/traces/kernel | grep - > > A10 '^clock {' > > > > and copy the output to the Redmine issue's description. > > 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. Thank you, Phil > }; > > typealias integer { > size = 27; align = 1; signed = false; > > > > > BR, > > > > Phil > > Best regards, > Seongab
WARNING: multiple messages have this Message-ID (diff)
From: Philippe Proulx via lttng-dev <lttng-dev@lists.lttng.org> To: "Kim, Seongab" <Seongab.Kim@harman.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 10:00:29 -0400 [thread overview] Message-ID: <CAB4xu_1p0AYHhb1GASzOM9e-pdWmSkeTfZq2tQoyacso1MCUNA@mail.gmail.com> (raw) Message-ID: <20200723140029.rH6cY-XjkdOyurR5gjZWZmCZLk0BQQw1KX2zXiFfvZU@z> (raw) In-Reply-To: <7cb6526a78a9468e969a0fe36f42c6d7@HIMDWSMB06.ad.harman.com> On Thu, Jul 23, 2020 at 5:09 AM Kim, Seongab <Seongab.Kim@harman.com> wrote: > > Hello Phil, > > > -----Original Message----- > > From: Philippe Proulx <eeppeliteloop@gmail.com> > > Sent: Wednesday, July 22, 2020 5:06 PM > > To: Kim, Seongab <Seongab.Kim@harman.com> > > Cc: lttng-dev@lists.lttng.org > > Subject: [EXTERNAL] Re: [lttng-dev] babeltrace cannot open the trace but > > Trace Compass can open > > > > Thank you for the bug report. > > > > Can I kindly ask you to create an official issue for this? > > > > Go to > > <https://clicktime.symantec.com/38qgEsYhBTfCNnYpLPoAn647Vc?u=https% > > 3A%2F%2Fbugs.lttng.org%2Fprojects%2Fbabeltrace%2Fissues%2Fnew>. > > > > I'd also like you to attach the offending CTF trace so that I can analyze it if it > > doesn't contain sensitive data and is somewhat small. > > I created an account in Redmine, but I'm still waiting for the account activation mail. I tried to click the resend mail link two times without success. > Also the trace is big (1.4 GB) and it contains sensitive data. > > > If it's not possible, do: > > > > $ babeltrace2 -o ctf-metadata /mnt/ssd/work/skim/traces/kernel | grep - > > A10 '^clock {' > > > > and copy the output to the Redmine issue's description. > > 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. Thank you, Phil > }; > > typealias integer { > size = 27; align = 1; signed = false; > > > > > BR, > > > > Phil > > 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:00 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 [this message] 2020-07-23 14:00 ` 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 2020-07-23 14:10 ` [lttng-dev] " 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=CAB4xu_1p0AYHhb1GASzOM9e-pdWmSkeTfZq2tQoyacso1MCUNA@mail.gmail.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: linkBe 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).