Hello Mathieu,
thanks again.
On Wed, 2021-05-05 at 10:46 -0400, Mathieu Desnoyers wrote:
> > >
> > > So my understanding is that you implement your own call rcu
> > > worker
> > > thread because the
> > > one provided by liburcu leaks data structure on process exit, and
> > > you
> > > expect
On Wed, May 05, 2021 at 10:46:58AM -0400, Mathieu Desnoyers wrote:
> - On May 5, 2021, at 3:54 AM, Martin Wilck mwi...@suse.com wrote:
>
> > On Fri, 2021-04-30 at 14:41 -0400, Mathieu Desnoyers wrote:
> >> - On Apr 29, 2021, at 9:49 AM, lttng-dev
> >> lttng-dev@lists.lttng.org wrote:
> >>
- On May 5, 2021, at 3:54 AM, Martin Wilck mwi...@suse.com wrote:
> On Fri, 2021-04-30 at 14:41 -0400, Mathieu Desnoyers wrote:
>> - On Apr 29, 2021, at 9:49 AM, lttng-dev
>> lttng-dev@lists.lttng.org wrote:
>>
>> > In multipath-tools, we are using a custom RCU helper thread, which
>> >
On 2021-05-04 9:57 p.m., Simon Marchi via lttng-dev wrote:
> I tried to see if it would be possible for you
> to just not use packets, but unfortunately I stumbled on what looks like
> a bug in the CTF metadata parser, it hardcodes whether streams classes
> have packets to true:
>
>
>
On Fri, 2021-04-30 at 14:41 -0400, Mathieu Desnoyers wrote:
> - On Apr 29, 2021, at 9:49 AM, lttng-dev
> lttng-dev@lists.lttng.org wrote:
>
> > In multipath-tools, we are using a custom RCU helper thread, which
> > is cleaned
> > out
> > on exit:
> >
> >
Hi,
I have a memory leak some where in my c++ application. Since it was
written in c++98 there are lot of pointer passed back and forth and there
is no clear ownership of the pointers. I was wondering if it's possible to
check for memory leak and give a value sections to probe for the leak
