From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: Handling of L and ll prefixes different from glibc
Date: Wed, 14 Dec 2016 22:01:59 -0600 [thread overview]
Message-ID: <585215B7.2070507@adelielinux.org> (raw)
In-Reply-To: <20161215023042.GW1555@brightrain.aerifal.cx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 14/12/16 20:30, Rich Felker wrote:
> It's true that some programs which are just misusing printf format
> specifiers as part of unnecessary status/debug/junk output will
> fully work now, despite having UB, and that they would stop working
> with such a change. But in most cases, the lack of output now, even
> if it's unnoticed, is a bug that could have serious consequences.
> For example missing output in text that's parsed and used in a
> script can lead to things like rm -rf'ing the wrong directory. So I
> tend to think always failing hard and catching the bug is
> preferable.
Yeah, I can understand that. Just makes me nervous as a package
maintainer is all :)
> BTW I wonder if gcc's -Wformat catches these errors.
It is meant to. I know that clang whines loudly on mismatched format
specifiers, and I seem to recall it even whines on format specifiers
that don't exist, but it has been a while since I checked GCC's.
- --arw
- --
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJYUhWyAAoJEMspy1GSK50UX9QP/0EhqwhljRAm3yY5Glhl2emt
R0FtBYsHHDhnqkjPJ4AWV3z6eVCPb2nd9RZYGpj778rFl/nOijfR8ilzUL7sKYGJ
KXiBx5N0cOWpm75RWGKwvAEEkoC4zqQZ4HbyK13RzWdO6rJPieb137UW7sKw+S7C
I7S4PRbd09pBd9Uk1smDEEknbLxDwUbARJaFOuChzzGgZU0AOfnSg7FgOGEPv+va
1dBB98gIAcMkhSOy3xBZsMZWr0frpXiym119Y2IHP56xkoIQGN585ChluEWa54tt
pHEXYsDIT5ZOMMdZqIbllI3mFILopZ3PalrBiLTKwqqnAyhkRyZNWTTTxtdm7aNx
iARmCXupxk1boNYjBcsQhc25EZg6tRUebHveSKfoDxKALRu+YGtEcWg+um/29L78
Jz1G4D9nAExoUVBKGkxxG6VlTEUBdmVd6pCWdm08GzX0QJaq0aA1KBK+0lexDluV
eqZfG+J40bwWhFuI3hNpKy46UHs+mDPgGPzCaGWupMAYaYLAo5UCnMqIAOSFMWed
hwwNlwUCA8hwjXcq6nsWa3B2lIt5LmioAfZQ4+8WtiEfU5Kwzjw66olSF1uwdNMh
q4g7Sju81oUOWEFId7Dy+zBah5XZt+nyRL/6QSob9WKz5hXb30WZinHH6M+m1z4F
RAPqzt4nfGqMhRfBY2vL
=5CdV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-12-15 4:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 13:46 Nadav Har'El
2016-12-14 16:13 ` Rich Felker
2016-12-14 17:17 ` Szabolcs Nagy
2016-12-14 22:37 ` A. Wilcox
2016-12-15 2:30 ` Rich Felker
2016-12-15 4:01 ` A. Wilcox [this message]
2016-12-15 11:30 ` Szabolcs Nagy
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=585215B7.2070507@adelielinux.org \
--to=awilfox@adelielinux.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).