ddiss at samba.org
Fri Jun 15 12:43:32 UTC 2018
On Fri, 15 Jun 2018 14:29:58 +0200, Volker Lendecke wrote:
> > In talloc we already have a very nice hierarchical allocator which,
> > alongside the stack, is perfectly capable of providing short lived
> > memory allocations.
> How do we make sure we don't leak this memory, short of the clear
> convention using talloc_tos()?
A convention of using talloc_tos() does not guarantee that we don't
leak memory. Just like long running async state contexts, talloc
stackframes can also be neglected. As mentioned in the other mail, my
preference would be to proceed with integration of valgrind memcheck,
massif and talloc_report into regular CI.
More information about the samba-technical