talloc()

[Luke Kenneth Casson Leighton]

On Fri, 11 Aug 2000, Andrew Tridgell wrote:

> Luke,
> 
> nope, that makes no sense. There is no allocated area when you ask for
> zero bytes.

zero bytes returns NULL?

> btw, if what you want is guard regions around all non-zero sized
> allocs then that is normally a good idea, but doesn't actually work
> for talloc(). In a normal alloc there is a free() fn, and the free fn
> can check the guard areas and give a warning if they are corrupted. In
> the case of talloc there is no free fn so the guard areas would be
> useless.

... i wasn't thinking of automated guard area checking.

... actually, if you were, then it would be possible to do this on
talloc_destroy().  using the cliffs version of talloc.c [not the samba
version]