From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Handling of L and ll prefixes different from glibc
Date: Wed, 14 Dec 2016 18:17:57 +0100 [thread overview]
Message-ID: <20161214171756.GH16379@port70.net> (raw)
In-Reply-To: <20161214161348.GU1555@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2016-12-14 11:13:48 -0500]:
> behavior. I'm mildly leaning towards causing a crash on invalid format
> strings so that the location of the incorrect usage can be quickly
> found with a debugger, but I'd like feedback from users who've
> debugged this sort of thing on whether that'd actually be helpful.
crashing sounds good to me.
next prev parent reply other threads:[~2016-12-14 17:17 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 [this message]
2016-12-14 22:37 ` A. Wilcox
2016-12-15 2:30 ` Rich Felker
2016-12-15 4:01 ` A. Wilcox
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=20161214171756.GH16379@port70.net \
--to=nsz@port70.net \
--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).