Re: [MiNT] malloc() bug ?

[Vincent Rivière <vincent.riviere@freesbee.fr>]

Miro Kropacek wrote:
> I'm not sure if you're right -- kernel has much more trace outputs, so 
> we can see some special condition has happened (for example allocation 1 
> byte behind page boundary, N bytes long biggest available block, number 
> of block or anything else, I'm just guessing). But of course, debug 
> mintlib + debug kernel may be the best option.

Do the MiNTLib malloc() call the kernel malloc every time ? I'm 
absolutely not sure about that. That looks like a problem in the malloc 
implementation in the MiNTLib. And it is quite complicated.

--
Vincent Rivière