[lttng-dev] state tracking and missing statedump end

[Alexandre Montplaisir]

Hi Mathieu,

Thanks for the info, good to know!

However, we (in Trace Compass) don't actually make use of the 
"statedump_end" event. Should we?

For now, we only use the "lttng_statedump_process_state" events in our 
state model. The information contained in these events is applied to the 
state of the involved process. This state becomes valid starting at the 
timestamp of each statedump event.

What type of information does the "lttng_statedump_end" event implies?

Cheers,
Alex


On 2015-05-14 06:35 PM, Mathieu Desnoyers wrote:
> Hi Alexandre, Hi Matthew,
>
> You will certainly be interested in this commit in
> lttng-modules:
>
> commit 84c7055e17f9bf7628fe1004db732d932ed2a77b
> Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> Date:   Thu May 14 18:29:58 2015 -0400
>
>      Fix: missing statedump end event when block device listing available
>      
>      Incorrect handling of lttng_enumerate_block_devices() return value of 0
>      (which means "ok"), causing do_lttng_statedump() to return early.
>      
>      To causes missing "lttng_statedump_end" in traces where block device
>      enumeration is available (CONFIG_KALLSYMS=y).
>      
>      Reported-by: Antoine Busque <abusque at efficios.com>
>      Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
>
> Thanks,
>
> Mathieu
>