id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
86	keeping psMemBlock elements around forever?	robert.desonia@…	eugene	"SDRS states, ""In order to trace double frees and other memory errors, the memory
block reference is not automatically deleted when the associated memory is
deleted. Rather, the psMemBlock data and endpost data are left behind. If
endpost points to the memory location immediately following the psMemBlock data,
then the memory block has been freed. This state must be enforced by psFree.""

This doesn't seem to be a real good idea, as this is nothing more than a
designed memory leak.  If you delete the whole memory block, a second psFree
generally generates either a segmentation fault or a memory corruption
detection, which seems to be just as good of a detection means as a psAbort,
though not as friendly of an error message.

If this is a 'must have', I'd recommend that such functionality should be able
to be turned off, in the same manner as the tracing functionality, as compile time.

N.B. I've not implemented this feature yet.  I'll await your input before doing
anything in this regard.

-rdd"	defect	closed	high		PSLib SDRS	unspecified	normal	fixed