Thanks for the replies to those who knew about how the internals of malloc work.
The original question was, 'is there an malloc bug?', after malloc stoped
working when a programming error wrote past the end of an allocated block.
The consensus answer was that there is no bug in malloc. The overrunning of the
allocated space trashed some internal data that malloc() and free() need and led
to the failure.
So the failure was an artifact of the programming error rather than a bug.
There is no danger to others dataspace.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:47 CDT