While we are into this discussion, what about implementing a kind of
purify in NetBSD ?

This would trap overflows in gets() as well as many other obscure
bugs in memory management...

[ For those who don't know purify, it's a commercial product that allows
a run-time debugging of memory allocation problems (writing past an
malloc'ed block or to a free'd block, freeing a block twice, reading
uninizialized memory...) by trapping all malloc calls and all memory
references at run time. ]


					Matthieu

------------------------------------------------------------------------------