Re: [lttng-dev] decoding tracef msg string via babeltrace API

On Tuesday, April 9, 2019 7:02:06 PM CEST Jérémie Galarneau wrote: > On Tue, 9 Apr 2019 at 04:36, Milian Wolff wrote: > > On Thursday, April 4, 2019 8:25:51 PM CEST Jérémie Galarneau wrote: > > > Hi Milian, > > > > > > I have pushed a fix [1] in the stable-1.5 branch that addresses the > > > issu

Re: [lttng-dev] decoding tracef msg string via babeltrace API

On Wednesday, April 10, 2019 9:56:43 AM CEST Milian Wolff wrote: > On Tuesday, April 9, 2019 7:02:06 PM CEST Jérémie Galarneau wrote: > > On Tue, 9 Apr 2019 at 04:36, Milian Wolff wrote: > > > On Thursday, April 4, 2019 8:25:51 PM CEST Jérémie Galarneau wrote: > > > > Hi Milian, > > > > > > > > I

[lttng-dev] [PATCH lttng-modules 1/1] Fix: don't access packet header for stream_id and stream_instance_id getters

The stream ID and stream instance ID are invariant for a stream, so there is no point reading them from the packet header currently owned by the consumer (between get/put subbuf). Actually, the consumer try to access the stream_id from the live timer when sending a live beacon without getting the

[lttng-dev] [PATCH lttng-ust 1/1] Fix: don't access packet header for stream_id and stream_instance_id getters

The stream ID and stream instance ID are invariant for a stream, so there is no point reading them from the packet header currently owned by the consumer (between get/put subbuf). Actually, the consumer try to access the stream_id from the live timer when sending a live beacon without getting the

Re: [lttng-dev] [PATCH lttng-modules] RFC: fix: Remove start and number from syscall_get_arguments() args (v5.1)

merged into master, 2.11, 2.10, 2.9, thanks! Mathieu - On Apr 9, 2019, at 2:12 PM, Michael Jeanson mjean...@efficios.com wrote: > commit b35f549df1d7520d37ba1e6d4a8d4df6bd52d136 > Author: Steven Rostedt (Red Hat) > Date: Mon Nov 7 16:26:37 2016 -0500 > >syscalls: Remove start and n