LTTng » LTTng-tools

$ lttng create
$ lttng start
$ lttng enable-event ...
$ lttng stop
---> Failure

For kernel, see bug346.

For UST, when stopping the trace, a wonderful assert is triggered!

ust-app.c:2354: ust_app_stop_trace: Assertion `ua_sess->started == 1' failed

This is explained by the fact that on start, there is no kernel nor ust session so nothing exists until the enable event. The started flag is never set thus creating this code flow error triggered by the assert above.

When enabling an event, we need a way to know if a start command was already done when creating a newly UST/kernel session and start it if so.

This is critical thus making it a priority.