lttng_enable_event makes lttng freeze when then event is of type LTTNG_EVENT_ALL and with an unexisting name
if an event of type LTTNG_EVENT_ALL (-1) has a random name, such as "blabla", and lttng_enable_event is called with that event, it returns no error but it should.
As a result of this, for a session named "ses", lttng list ses will give: === Domain: Kernel ===
- channel0: [enabled]
overwrite mode: 0
subbufers size: 262144
number of subbufers: 4
switch timer interval: 0
read timer interval: 200
(loglevel: TRACE_EMERG (0)) (type: tracepoint) [disabled]
and then destroy all sessions.
If lttng list ses is not called, but instead the session is started, then it is goodbye lttng, see you next reboot.