Hi Evan,
It turns out it's a Babeltrace 2 bug. Here the fix:
https://review.lttng.org/c/babeltrace/+/6257.
It should be merged into the master and stable-2.0 branches soon.
Thank you for reporting the issue,
Francis
On 8/4/21 3:55 AM, Evan Galea wrote:
Hi Francis, thanks for your reply. A
Hi Evan,
On 8/1/21 5:11 AM, Evan Galea via lttng-dev wrote:
Hi there
Thanks for help on my previous issue. I was able to get
callstack-user to work and see it in my traces. However, in order to
get it to run I needed to enable-event --kernel all. Is it necessary
to have all kernel events ena
Hi,
You see this "Unknown value 33" because there are no label with the
value 33 in the "block_rq_type" enumeration.
More specifically, you see the value "33" because it's the result of two
OR-ed bitflags (RWBS_FLAG_WRITE | RWBS_FLAG_SYNC).
The type of the "rwbs" field in the event was chan
Hi Changcheng,
This is not currently supported by Babeltrace. It could probably be done
the same way we do it with the "ip" and "vpid" contexts in the debug-info
component class but it's not done yet.
Thanks,
Francis
Le mer. 1 juill. 2020, à 11 h 58, Liu, Changcheng via lttng-dev <
lttng-dev@lis