This is the mail archive of the
mailing list for the newlib project.
Re: first post, perplexed by printf()
- From: Dave McGuire <mcguire at neurotica dot com>
- To: newlib at sourceware dot org
- Date: Tue, 07 Oct 2014 01:24:00 -0400
- Subject: Re: first post, perplexed by printf()
- Authentication-results: sourceware.org; auth=none
- References: <542E1B16 dot 8050503 at neurotica dot com> <542E4C7D dot 3030500 at op dot pl> <5431AD5C dot 4040705 at neurotica dot com> <BLU436-SMTP110C267DFABCD15EE00252EF9A50 at phx dot gbl>
On 10/06/2014 04:30 AM, Federico Terraneo wrote:
>> Ok, I will hack on this a bit today and see how far I get. The
>> linker script and startup code I'm using are the ones distributed
>> by SiLabs for this family of processors. At first glance, your
>> linker script and startup code are very different from those.
> This is just a guess, as I have not seen the SiLabs linker script, but
> have you tried if malloc works on your platform, such as trying to
> allocate some blocks, writing into them and seeing if it makes the
> system crash? I've seen some linker script in the past, provided by
> chip manufacturers, which fail to set up a working heap, and printf
> calls malloc internally.
Hi! I got sidetracked by other work last night and today, and didn't
get very far in my efforts. I'll take another stab at it tomorrow.
But as far as malloc(), that's working fine, and I just verified it
again (to make sure the compiler wasn't optimizing it out, etc). I'm
able to malloc() a 4K chunk of memory and initialize it in a loop.
Dave McGuire, AK4HZ/3
New Kensington, PA