Just to confirm, I think using lsan allocator simply means don't to
implement the custom allocator, but just using the existing APIs to
malloc/free to deal with the memory.
I think we can probably do that. The issue is this is some third party
code(dpdk.org). We probably have to introduce some lsa
Forgot to add Ming to reply.
11 Окт 2016 г. 22:35 пользователь "Maxim Ostapenko"
написал:
>
> Hi,
>
> 11 Окт 2016 г. 21:12 пользователь "Ming Zhao"
написал:
> >
> > Hi,
> >
> > I'm trying to figure out a way to let a custom allocator be able to
> > report leaked object through lsan.
> > Presum
Hi,
11 Окт 2016 г. 21:12 пользователь "Ming Zhao"
написал:
>
> Hi,
>
> I'm trying to figure out a way to let a custom allocator be able to
> report leaked object through lsan.
> Presumably we could just do everything in the allocator since it's
> customized already. But we don't really want to re
Hi,
I'm trying to figure out a way to let a custom allocator be able to
report leaked object through lsan.
Presumably we could just do everything in the allocator since it's
customized already. But we don't really want to repeat the effort that
has been done by lsan like tracking the live object,
