From: Federico Terraneo <fede.tft@hotmail.it>
To: newlib@sourceware.org
Subject: Re: first post, perplexed by printf()
Date: Mon, 06 Oct 2014 08:30:00 -0000 [thread overview]
Message-ID: <BLU436-SMTP110C267DFABCD15EE00252EF9A50@phx.gbl> (raw)
In-Reply-To: <5431AD5C.4040705@neurotica.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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.
>
Hi,
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)
iF4EAREIAAYFAlQyUx8ACgkQbTKLH9en/LsZ9gD/Ri+4qk3Ne20e/RSsfOQ+DNeO
uycjcGKNHMZKYTyyV/sA/1EtrO02I+z+LicJT/V++fso+3wFtVSl5iCvRbZlA/3A
=3XfA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-10-06 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 3:42 Dave McGuire
2014-10-03 7:13 ` Freddie Chopin
2014-10-05 20:43 ` Dave McGuire
2014-10-06 8:30 ` Federico Terraneo [this message]
2014-10-07 5:24 ` Dave McGuire
2014-10-07 13:06 ` Jonathan Roelofs
2014-10-08 16:36 ` Dave McGuire
2014-10-08 18:04 ` Jonathan Roelofs
2014-10-08 19:12 ` Dave McGuire
2014-10-08 22:06 ` Jeff Johnston
2014-10-09 18:26 ` David Fernandez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU436-SMTP110C267DFABCD15EE00252EF9A50@phx.gbl \
--to=fede.tft@hotmail.it \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).