Solution to "oops, corrupted memory again!"

[Bjorn Benson]

In article <4495 at cbrma.UUCP> trl at cbrma.UUCP (Tom Lanning) writes:
>	Are there any "malloc" routines that check for modification of
>malloc's link pointers by the "user's" code?  ....
>	I am interested in any tools, recommendations, or routines that may
>help.  Thanks.

I have a data abstraction package that I wrote that helps with this
problem.  I posted it to net.sources.  Hope it helps...

					Bjorn Benson
					FutureNet, a Data I/O company