[lttng-dev] Workflow to view old and current trace data

Hi, long time no see! Consider a system that's recording trace data continuously from a userspace application. A problem is noticed and I'd like to investigate it. What workflow would allow me to view past trace data to analyze the cause of the problem and view current (live) trace data while work

[lttng-dev] [RFC PATCH lttng-tools] Fix: relayd: Swap endianness of packet index

The packet index in stream_update_index() is meant to be stored to disk, and therefore is kept in big endian. Swap its endianness to host endian before using it internally. Fixes "Fix: relayd: use packet sequence number for rotation position". Signed-off-by: Mathieu Desnoyers --- src/bin/lttng

Re: [lttng-dev] Workflow to view old and current trace data

- On Nov 8, 2019, at 3:49 AM, Benjamin Poirier benjamin.poir...@gmail.com wrote: > Hi, long time no see! > > Consider a system that's recording trace data continuously from a > userspace application. A problem is noticed and I'd like to investigate > it. What workflow would allow me to view

Re: [lttng-dev] [PATCH lttng-ust] Require automake >= 1.12

Merged into master branch, thanks! Mathieu - On Nov 7, 2019, at 1:48 PM, Michael Jeanson mjean...@efficios.com wrote: > The test suite LOG_DRIVER statement requires that automake >= 1.12 be used > during bootstrap. > > Signed-off-by: Michael Jeanson > --- > configure.ac | 2 +- > 1 file cha

Re: [lttng-dev] [PATCH urcu] Require automake >= 1.12

Merged into master branch, thanks! Mathieu - On Nov 7, 2019, at 1:39 PM, Michael Jeanson mjean...@efficios.com wrote: > The test suite LOG_DRIVER statement requires that automake >= 1.12 be used > during bootstrap. > > Signed-off-by: Michael Jeanson > --- > configure.ac | 2 +- > 1 file cha