I'm not going anywhere. Double-free is a known pitfall. People watch for it and a lot of standard libraries have safeguards against it. On the other hand tfree

I'm not going anywhere. Double-free is a known pitfall. People watch for it and a lot of standard libraries have safeguards against it. On the other hand tfree() hangs if a prior call to talloc_set_parent() is passed certain arguments. Just more ammunition to shoot one's own foot. (p, p) might be a degenerate case, but real code will create cyclic references. In such case blaming programmer is the least productive way to handle it.