mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: Re: New static analysis results
Date: Fri, 5 Sep 2014 22:39:45 +0400 (MSK)	[thread overview]
Message-ID: <alpine.LNX.2.00.1409052217200.30149@monopod.intra.ispras.ru> (raw)
In-Reply-To: <20140905180252.GO23797@brightrain.aerifal.cx>

On Fri, 5 Sep 2014, Rich Felker wrote:
> > > ctime.c:5
> > >     localtime(t) may return NULL, but that will cause UB in asctime
> > 
> > Yes, I need to look into what ctime should do in this case though...
> 
> Found it:
> 
>   7.27.3.2 The ctime function
> 
>   2 The ctime function converts the calendar time pointed to by timer
>   to local time in the form of a string. It is equivalent to
> 
>            asctime(localtime(timer))
> 
> The standard basically specifies the implementation, so it's clearly
> UB if localtime(t) would return a null pointer. Looks like no action
> is needed here; the most-desirable-behavior (crash) for UB happens
> automatically anyway.

I suspect what happened is, at some point localtime was not specified to
return NULL and set errno, and at that time it made perfect sense to specify
asctime as you quoted, and then at some later point localtime specification
was expanded with error cases, but asctime specification was not adjusted.
Is that possible?

It doesn't look very nice for a libc to invoke UB where it could easily
propagate error to the caller, but "that's exactly what the standard requires"
can't be argued with I guess.

Alexander


  reply	other threads:[~2014-09-05 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 16:45 Alexander Monakov
2014-09-04 17:13 ` Rich Felker
2014-09-05 18:02   ` Rich Felker
2014-09-05 18:39     ` Alexander Monakov [this message]
2014-09-05 18:53       ` Rich Felker
2014-09-05 20:50         ` Jens Gustedt
2014-09-05 21:23           ` Rich Felker

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=alpine.LNX.2.00.1409052217200.30149@monopod.intra.ispras.ru \
    --to=amonakov@ispras.ru \
    --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).