Probably if the pictures had
*__malloc_heap_end == __heap_end
instead of
__malloc_heap_end == __heap_end
that would do the trick. At least in my mind.
Steve
On 3/29/07, Joerg Wunsch <[EMAIL PROTECTED]> wrote:
Update of bug #19445 (project avr-libc):
Category: None => Documentation
Item Group: Unknown => Documentation
_______________________________________________________
Follow-up Comment #1:
As Dave Hylands already wrote on avr-libc-dev, __malloc_heap_end
is a variable that points to __heap_end, so you are only ever
supposed to handle __heap_end. The __malloc_* variables are
what malloc() uses internally to keep track of the allocations
and boundaries.
This is basically also the way the documentation tells you,
but in retrospect, I agree the picture is a little misleading
here, and could express that clearer.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?19445>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
--
Steve Franks, KE7BTE
Staff Engineer
La Palma Devices, LLC
http://www.lapalmadevices.com
(520) 312-0089
_______________________________________________
AVR-libc-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
