Hi Steve,
00803c18 D __malloc_heap_start
00803c1a D __malloc_heap_end
I'm looking at the avrlibc docs right now, and they seem to indicate that my
makefile should be instructing both heap_end and malloc_heap_end to be at
0x80A0FF.
Looking at the source code of avr-libc, it seems that
On 3/29/07, Dave Hylands [EMAIL PROTECTED] wrote:
Hi Steve,
00803c18 D __malloc_heap_start
00803c1a D __malloc_heap_end
I'm looking at the avrlibc docs right now, and they seem to indicate
that my
makefile should be instructing both heap_end and malloc_heap_end to be
at
0x80A0FF.
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
org] On Behalf Of Steve Franks
Sent: Thursday, March 29, 2007 10:00 AM
To: Dave Hylands
Cc: avr-libc-dev@nongnu.org
Subject: Re: [avr-libc-dev] I thought I understood malloc
Well, last night I added:
URL:
http://savannah.nongnu.org/bugs/?19445
Summary: _malloc_heap_end does not follow _heap_end on m2561
Project: AVR C Runtime Library
Submitted by: None
Submitted on: Thursday 03/29/2007 at 18:02 UTC
Category: None
Update of bug #19445 (project avr-libc):
Category:None = Documentation
Item Group: Unknown = Documentation
___
Follow-up Comment #1:
As Dave Hylands
As Dave Hylands wrote:
So it's the contents of __malloc_heap_end not the address of
__malloc_heap_end that points to __heap_end.
Right. As I wrote in the followup to the bug report, I agree the
picture is a bit misleading here, though the remainder of the
documentation explains that. I'm
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:
As Steve Franks wrote:
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.
It has a point, but it's not very exact either: it suggests
__malloc_heap_end were a pointer which
It has a point, but it's not very exact either: it suggests
__malloc_heap_end were a pointer which it isn't.
You did earlier say 'it's a variable that points to heap_end', however.
Hence the confusion, I think?
Steve
___
AVR-libc-dev mailing list
