From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
To: "(GalaxyMaster)" <galaxy@openwall.com.au>
Cc: musl@lists.openwall.com
Subject: Re: [musl] strtoll() incompatibility
Date: Wed, 13 Oct 2021 16:28:45 +0200 [thread overview]
Message-ID: <20211013162845.6597e45f@inria.fr> (raw)
In-Reply-To: <0100017c79f9d219-86b8d3e7-358a-473c-9736-befc0678d7c7-000000@email.amazonses.com>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
Hello,
on Wed, 13 Oct 2021 14:06:27 +0000 you ("(GalaxyMaster)"
<galaxy@openwall.com.au>) wrote:
> Hello,
>
> I am not a true developer, so I don't have the POSIX standard handy,
> hence could not quickly find whether the observed behaviour is
> correct or not. I have two systems, one is musl-based and the other
> is Glibc-based, so every time I stumble upon something I check
> against Glibc. I know that Glibc developers did quite a few bespoke
> things, but this particular one made me wonder whether it is a bug in
> musl.
>
> Longs story short, it seems that musl's strto*() set errno when it is
> unable to find a legitimate number at the begining of the string:
> ...
This function is actually in C, but the possible `errno` specification
comes seemingly from POSIX:
The implementation may also set errno to EINVAL in case no
conversion was performed (no digits seen, and 0 returned).
Jₑₙₛ
--
:: INRIA Nancy Grand Est ::: Camus ::::::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536 ::
:: :::::::::::::::::::::: gsm France : +33 651400183 ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2021-10-13 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 14:06 (GalaxyMaster)
2021-10-13 14:22 ` Shiz
2021-10-13 14:58 ` (GalaxyMaster)
2021-10-13 14:28 ` Jₑₙₛ Gustedt [this message]
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=20211013162845.6597e45f@inria.fr \
--to=jens.gustedt@inria.fr \
--cc=galaxy@openwall.com.au \
--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).