From: Andreas Schwab <schwab@suse.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Simon Chopin <simon.chopin@canonical.com>, libc-alpha@sourceware.org
Subject: Re: UB status of snprintf on invalid ptr+size combination?
Date: Wed, 15 Mar 2023 10:22:16 +0100 [thread overview]
Message-ID: <mvmy1nyz7w7.fsf@suse.de> (raw)
In-Reply-To: <a5bda742-c534-f5a6-abba-39d29c26f01e@cs.ucla.edu> (Paul Eggert's message of "Tue, 14 Mar 2023 14:39:42 -0700")
On Mär 14 2023, Paul Eggert wrote:
> For example, it's valid for snprintf to be implemented this way:
>
> int
> snprintf (char *buf, size_t size, char const *fmt, ...)
> {
> char *buf_limit = buf + size;
> ...
> }
>
> even though this would have undefined behavior if BUF points to a
> character array smaller than SIZE.
Since it is part of the implementation it is irrelevant from the POV of
the standard. The implementation does not have to abide to the C
standard, as long as it properly implements the interface constraints.
What matters is the wording of the standard. The POSIX standard is more
explicit here: "with the addition of the n argument which states the
size of the buffer referred to by s." Probably the C standard should be
clarified.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-03-15 9:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 19:47 Simon Chopin
2023-03-14 21:39 ` Paul Eggert
2023-03-15 9:22 ` Andreas Schwab [this message]
2023-03-15 15:54 ` Siddhesh Poyarekar
2023-03-15 18:34 ` Michael Hudson-Doyle
2023-03-19 14:45 ` manfred
2023-03-19 23:07 ` Vincent Lefevre
2023-03-20 12:05 ` Siddhesh Poyarekar
2023-03-20 12:17 ` Alejandro Colomar
2023-03-20 12:29 ` Siddhesh Poyarekar
2023-03-20 13:36 ` Vincent Lefevre
2023-03-20 13:50 ` Vincent Lefevre
2023-03-20 16:56 ` Siddhesh Poyarekar
2023-03-20 17:36 ` Vincent Lefevre
2023-03-20 15:09 ` Vincent Lefevre
2023-03-20 16:15 ` Alejandro Colomar
2023-03-20 16:33 ` Vincent Lefevre
2023-03-20 17:00 ` Vincent Lefevre
2023-03-20 17:31 ` Siddhesh Poyarekar
2023-03-20 17:45 ` Vincent Lefevre
2023-03-15 12:39 ` Vincent Lefevre
2023-03-16 10:29 ` Stephan Bergmann
2023-03-18 2:07 ` Vincent Lefevre
2023-03-18 2:30 ` Alejandro Colomar
2023-03-18 10:58 ` Vincent Lefevre
2023-03-18 15:01 ` Andreas Schwab
2023-03-19 22:48 ` Vincent Lefevre
2023-03-19 23:24 ` Andreas Schwab
2023-03-20 4:10 ` Vincent Lefevre
2023-03-20 9:19 ` Andreas Schwab
2023-03-20 10:42 ` Vincent Lefevre
2023-03-20 10:44 ` Andreas Schwab
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=mvmy1nyz7w7.fsf@suse.de \
--to=schwab@suse.de \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=simon.chopin@canonical.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.
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).