[PATCH] Do not leave random talloc magic in free()'ed memory, fix abort message

David Disseldorp ddiss at suse.de
Fri Jan 12 23:00:19 UTC 2018

On Fri, 12 Jan 2018 13:48:15 +1300, Andrew Bartlett via samba-technical wrote:

> +		talloc_log("talloc: access after free error - first free may be at %s\n", tc->name);

If the talloc_chunk is potentially invalid here, then I'd prefer to
avoid logging any strings off it. Should we make this a "...%p\n", tc)
instead, or am I being overly paranoid?

Cheers, David

More information about the samba-technical mailing list