Works as expected.
Thanks,
Paul
On 12/16/2013 02:39 PM, Mathieu Desnoyers wrote:
> Hi Paul,
>
> I rewrote the patch to use a reference counting approach instead.
> The effect should be the same. Here is the commit:
>
> commit f0cc794d37abf59b4b8079612c7aa03dc305d92f
> Author: Mathieu Desnoyers
>
Hi Paul,
I rewrote the patch to use a reference counting approach instead.
The effect should be the same. Here is the commit:
commit f0cc794d37abf59b4b8079612c7aa03dc305d92f
Author: Mathieu Desnoyers
Date: Mon Dec 16 08:36:06 2013 -0500
Fix: baddr_statedump tracepoint registration
Also make sure that the ust_baddr_statedump probe get registered prior
to using the tracepoint in lttng_ust_baddr_statedump(). This fix solves
the issue that in rare cases the very first ust_baddr_statedump events
were missing.
Signed-off-by: Paul Woegerer
---
include/lttng/ust-tracepoint-event.
- Original Message -
> From: "Paul Woegerer"
> To: lttng-dev@lists.lttng.org, "mathieu desnoyers"
>
> Sent: Tuesday, December 10, 2013 8:07:51 AM
> Subject: [PATCH] Fix: baddr_statedump tracepoint registration
>
> Ensure baddr_statedump tracepoint registration is completed prior to
> us
Ensure baddr_statedump tracepoint registration is completed prior to
using the tracepoint in lttng_ust_baddr_statedump().
Make liblttng-ust-dl robust for explicit baddr_statedump tracepoint
deregistration in lttng_ust_cleanup() (prevent dlopen/dlclose to get
traced if ust_baddr tracepoints are not
