Which was fixing this issue, amongst other things.
[ This fix should be applied to Babeltrace stable 1.3 and 1.4 only. ]
[ This v2 patch removes error checking that was introduced in v1. Since
the callees don't distinguish between -ENOENT and -EINVAL errors,
we don't know if we need to error out or not. Keep the original
1.x behavior (no error checking). ]
When the standard output is redirected to a file, we need to flush the
output between each packet, otherwise the stream buffering may keep us
from seeing events for a while in a low-throughput trace.
While we are there, document that lttng-live does now support the
--output option in babeltrace 1.x.
e11a3d2...
by
Julien Desfossez <email address hidden>
Fix: lttng-live data_size and version endianness
The data_size and cmd_version fields need to be sent in network byte
order to the relay. These fields are currently ignored by the relay
because the commands have a fix-sized payload so it does not cause any
problem for now, but they may be used in the future, so we should avoid
any confusion.