This is the mail archive of the
mailing list for the newlib project.
Re: first post, perplexed by printf()
- From: Federico Terraneo <fede dot tft at hotmail dot it>
- To: newlib at sourceware dot org
- Date: Mon, 6 Oct 2014 10:30:26 +0200
- 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>
-----BEGIN PGP SIGNED MESSAGE-----
On 05/10/2014 22:43, Dave McGuire 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
-----END PGP SIGNATURE-----