From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] strings: use puts() rather than printf()
Date: Wed, 05 Nov 2008 11:14:15 -0600 [thread overview]
Message-ID: <4911D467.4020907@freescale.com> (raw)
In-Reply-To: <1225832627-10248-1-git-send-email-vapier@gentoo.org>
Mike Frysinger wrote:
> When running `strings` on really long strings, the stack tends to get
> smashed due to printf(). Switch to puts() instead since we're only passing
> the data through.
...which raises the question of why we don't have vsnprintf().
-Scott
next prev parent reply other threads:[~2008-11-05 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 21:03 [U-Boot] [PATCH] strings: use puts() rather than printf() Mike Frysinger
2008-11-04 21:03 ` [U-Boot] [PATCH v2] cmd_elf: CONFIG_ELF_SIMPLE_LOAD: load ELFs according to PHDRs Mike Frysinger
2008-11-05 17:14 ` Scott Wood [this message]
2008-12-07 0:17 ` [U-Boot] [PATCH] strings: use puts() rather than printf() Wolfgang Denk
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=4911D467.4020907@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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