Hi Zhenyu,
LTTng 2.7.0 has introduced event name wildcard support to kernel
space. In your specific case, the reason you see the call sequence
being so different is because we used to list all events and enable
them one by one.
Nowadays, we simply use the "enablers" mechanism, which has been
avai
Sorry，forget to post the verbose logs of lttng-sessiond.
DEBUG3 - 10:05:34.476087 [15262/15262]: Looking for a kernel consumer at these
locations: (in spawn_consumerd() at main.c:2516)
DEBUG3 - 10:05:34.476595 [15262/15262]: 1)
/usr/local/lib/lttng/libexec/lttng-consumerd (in spawn_consum
