| Newsgroups |
gmane.os.ecos.patches |
| Message-ID |
<[email protected]/> |
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001814
--- Comment #21 from Ilija Kocho <[email protected]> ---
(In reply to comment #20)
> I printed out dlmalloc.cxx before I retired for the day and read some of the
> description. I can't understand how this code with the large malloc ever
> worked. Given the 26K heap, and the allocation up to 4K chunks, no chunk
> should ever have been large enough unless it can append chunks, which my
> understanding is that it can't do that.
>
> Given that, I don't think I have any choice but to rewrite my algorithm to
> use a 4K buffer.
>
> So I can't find any reason not to commit this code, even if it breaks my
> code.
>
> However, if anyone has any idea how it could have worked, please enlighten
> me.
Mike
If the buffer is permanent, you may use staticaly allocated array. Also, FYI
Cortex-M specification requires stack to be 8 Byte aligned (though I haven't
experienced any anomaly with 4 Byte alignment so far).
Ilija
--
You are receiving this mail because:
You are on the CC list for the bug.