LTTng bugs repository

06/18/2018

11:41 AM Babeltrace Bug #1168: CTF for a user-plugged clock assumes that "offset" is unsigned, but a negative value can happen and will result in unparsable metadata getting stored

These v2.0 hurdles (new API, no docs, no examples) prevented us from confirming that this issue is gone in v2.0. I as... Vlad Roubtsov

06/02/2018

07:06 PM Babeltrace Bug #1168: CTF for a user-plugged clock assumes that "offset" is unsigned, but a negative value can happen and will result in unparsable metadata getting stored

Right. I've built babeltrace-2.0.0-pre4 (BTW, this required upgrading libpopt to v1.16, otherwise 'configure' is fine... Vlad Roubtsov

05/31/2018

05:52 PM Babeltrace Bug #1168 (Feedback): CTF for a user-plugged clock assumes that "offset" is unsigned, but a negative value can happen and will result in unparsable metadata getting stored

Hi,
I need to switch LTTng timestamp source to CLOCK_REALTIME from CLOCK_MONOTONIC in order to correlate with hard... Vlad Roubtsov

05/10/2018

01:15 PM LTTng-tools Bug #1160: contrary to docs, lttng-ust/tools do not provide LTTNG_TRACEPOINT_ENUM macro (without lttng-modules)

Hi Philippe,
Thanks for a very prompt response. You're correct. I can't believe I didn't spot TRACEPOINT_ENUM in t... Vlad Roubtsov

05/09/2018

06:53 PM LTTng-tools Bug #1160 (Resolved): contrary to docs, lttng-ust/tools do not provide LTTNG_TRACEPOINT_ENUM macro (without lttng-modules)

Greetings,
After going through the LTTng docs on how to build and install I chose to make a custom build of v2.10 ... Vlad Roubtsov