[lttng-dev] [EXTERNAL] Re: babeltrace cannot open the trace but Trace Compass can open

[Kim, Seongab]

Hello Phil,

> -----Original Message-----
> From: Philippe Proulx <eeppeliteloop at gmail.com>
> Sent: Wednesday, July 22, 2020 5:06 PM
> To: Kim, Seongab <Seongab.Kim at harman.com>
> Cc: lttng-dev at 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 at 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;
};

typealias integer {
        size = 27; align = 1; signed = false;

> 
> BR,
> 
> Phil

Best regards,
Seongab