LTTng » Babeltrace

When connecting a lttng-live component on a session with per-pid tracing and having one trace generating many events and another generating it results in no message at all being generated by the component.

The resulting traces on disk are readable.

BT1.5 prints the following:

[warning] Clock "(null)" offset differs between traces (delta 7650446431922014464 ns). Using average.

I suspect that the inactivity messages produced by the stream iterators of the silent trace triggers a bug in the ordering of messages. Maybe it's moving the timestamp of the last message too far ahead for other traces and it should only move it for that one silent trace.

1. Create 2 apps that loop and generate events
2. Create live per-pid session
3. Enable an event present in only one app
4. lttng start
5. launch both apps and let them loop.

Problem: One of the app generates events but we don't see them in the output of the lttng-live component.