I'm having a weird bug appear during boot. It is being triggered at
the first call of mm_free which comes from a call to mtdconfig driver.
I have enabled debug information and I'm also debugging at the point
before crash but since I don't understand the memory manager I can't
tell where this is coming from.
The assertion line is (mm_free.c:185):
DEBUGASSERT((node->preceding & ~MM_ALLOC_BIT) == prev->size);
The most common cause... in fact the only cause that I am aware of ...
for heap failure is memory corruption.
I normally debug this bay calling mallinfo() has selected places. If
the heap has been corrupted mallinfo() will fail. With a little effort
you can find the cause of the failure between the last good call to
mallinfo() and the first failed call to mallinfo().
