Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 27 Aug 2020 16:24:22 +0200
From: Jens Gustedt <>
Subject: Re: direct coding of asctime_r

on Thu, 27 Aug 2020 10:03:07 -0400 you (Rich Felker <>)

> I think the behavior of crashing on inputs that are UB and that can't
> safely be printed should probably be preserved, too; I'm not clear if
> you had that in mind already. I'm rather indifferent on what happens
> for inputs that are UB but that can faithfully be presented in the
> allotted space.

same for me

In the sample implementation I have "goto CLEANUP" and an implicit
guarantee that the output is always null terminated. This is more in
the spirit of `snprintf` not to do bad things as soon the output
buffer has at least 26 bytes.

But we could also do `abort()`, `do_crash()`, whatever fits into
musl's general strategy for error handling.


:: INRIA Nancy Grand Est ::: Camus ::::::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: ::

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.