> 
> However (and herein lies the problem) the call to morecore might need to add
> space for new indices, and this results in the old indices being freed via a
> call to _free_internal() in free.c. This is not normally a problem, except
> in the case where the old indices lay directly before the last free block.
> If this is the case, then _free_internal frees the old indices and combines
> it with last free block to produces a *new* free block whose starting point
> is no longer _heapinfo[block] (line 5: above). This means that we think we
> are updating part of the free chain, whereas in actual fact we are updating
> a now unused block.

I presume there is also the additional bug whereby the new indices are
allocated out of the free item that was at the end of the memory area?

	David

-- 
David Laight: david@l8s.co.uk