Re: [coldfire-gnu-discuss] Chasing RAM - libc ..
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldfire-gnu-discuss] Chasing RAM - libc ..
- To: m8847 <m8847@xxxxxx>
- Subject: Re: [coldfire-gnu-discuss] Chasing RAM - libc ..
- From: Daniel Jacobowitz <dan@xxxxxxxxxxxxxxxx>
- Date: Wed, 13 Oct 2010 11:34:34 -0400
On Wed, Oct 13, 2010 at 05:31:24PM +0200, m8847 wrote:
> .bss 0x2000fcac 0x34
> /home/micke/CodeSourcery/Sourcery_G++/bin/../lib/gcc/m68k-elf/4.4.1/../../../../m68k-elf/lib/m5208/libc.a(lib_a-mallocr.o)
> 0x2000fcac __malloc_top_pad
> 0x2000fcb0 __malloc_max_sbrked_mem
> 0x2000fcb4 __malloc_max_total_mem
> 0x2000fcb8 __malloc_current_mallinfo
>
> .data 0x20000350 0x410
> /home/micke/CodeSourcery/Sourcery_G++/bin/../lib/gcc/m68k-elf/4.4.1/../../../../m68k-elf/lib/m5208/libc.a(lib_a-mallocr.o)
> 0x20000350 __malloc_av_
> 0x20000758 __malloc_trim_threshold
> 0x2000075c __malloc_sbrk_base
Figure out what is bringing these in; you can tell from the -Map
output. The most likely cause is that you've redefined malloc but not
calloc.
--
Daniel Jacobowitz
CodeSourcery