Lines Matching refs:talloc_free
26 which is itself a child of mem_ctx. So if you do talloc_free(mem_ctx)
27 then it is all destroyed, whereas if you do talloc_free(X) then just X
28 and X->name are destroyed, and if you do talloc_free(X->name) then
33 talloc_free().
70 that if you talloc_free() the context then the new child disappears as
86 int talloc_free(void *ptr);
88 The talloc_free() function frees a piece of talloc memory, and all its
89 children. You can call talloc_free() on any pointer returned by
92 The return value of talloc_free() indicates success or failure, with 0
98 If this pointer has an additional parent when talloc_free() is called
105 talloc_free() operates recursively on its children.
112 talloc context and talloc_free()s only the children, not the context
132 - you can talloc_free() any parent of the original pointer. That
136 - you can talloc_free() the pointer itself. That will destroy the
150 Note that if the parent has already been removed using talloc_free()
154 Usually you can just use talloc_free() instead of talloc_unlink(), but
180 If your destructor attempts to talloc_free() the pointer that it is
181 the destructor for then talloc_free() will return -1 and the free will
214 the ptr is freed using talloc_free().
227 disappear before the ptr is freed with talloc_free().
285 talloc_realloc(context, ptr, type, 0) ==> talloc_free(ptr);