alloc problem?

[Bryce Schober]

Ping.

Bryce Schober wrote:

> Our arm-elf project here has been plagued with problems when trying to 
> use sprintf.  We've gotten by without it by writing some of our own 
> conversion functions, but ideally we'd be able to use c++, which would 
> need use alloc a lot.  My instinct tells me that alloc is the problem, 
> because the problems we've had with sprintf are fairly unpredictable and 
> it's the only function that we're using that needs an alloc.  
> Furthermore, I suspect that the root of the problem may be our linker 
> script (because the wierd behavior of sprintf has seemed to variy with 
> program size at times), but I know little about linker scripts, and 
> nothing about what the alloc functions require of one.
> 
> Here's our linker script:
> 
> SEARCH_DIR("/usr/local/src/arm-elf-gcc-combined/installs-combined/arm-elf/lib"); 
> 
> SECTIONS
> {
>     . = 0x00008000;
>     ER_RO : { *(ER_RO) }
>     .text : { *(.text ) }
>     .rodata : { *(.rodata) }
>     .data : { *(.data) }
>     __bss_start__ = .;
>     .bss : { *(.bss) }
> /*    __sbss_start = .; */
>     /*__sbss_end = .; */
>     __bss_end__ = .;
>     . += 0x4000;
> 
> PROVIDE (__stack = .);
>     _end = .;
>     end = .;
> /*
>     .debug_info     0 : { *(.debug_info) }
>        .debug_abbrev   0 : { *(.debug_abbrev) }
>        .debug_line     0 : { *(.debug_line) }
>        .debug_frame    0 : { *(.debug_frame) }
> */
> /*       .debug_str      0 : { *(.debug_str) } */
> /*       .debug_loc      0 : { *(.debug_loc) } */
> /*       .debug_macinfo  0 : { *(.debug_macinfo) } */
> }
> 
> 


-- 
Bryce Schober
Design Engineer
Dynon Avionics, Inc.
www.dynonavionics.com

---
[This E-mail scanned for viruses by digiposs.com]


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com