From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: setenv if value=NULL, what say standard? Bug?
Date: Thu, 23 Apr 2015 16:26:16 +0200 [thread overview]
Message-ID: <20150423142616.GA17440@port70.net> (raw)
In-Reply-To: <5538FA84.2060807@safe.ca>
* Jean-Marc Pigeon <jmp@safe.ca> [2015-04-23 09:58:28 -0400]:
> On 04/23/2015 09:22 AM, Szabolcs Nagy wrote:
> >
> > you are wrong, glibc actually corrupted then environ on NULL
> > argument and this was fixed recently
> >
> > http://sourceware.org/git/?p=glibc.git;a=commit;h=03c1e456b079929a8290aeb4aadb05c0df73bfd2
> >
> > stop mixing runtime failure with ub, that leads to nonsense
> > discussions.
> >
> glibc-2.12-1.132.el6_5.2.x86_64
> I do not confirm env corruption, try:
>
==6225== Invalid read of size 1
==6225== at 0x4C2BFC2: __GI_strlen (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==6225== by 0x4EA1F6B: puts (ioputs.c:37)
==6225== by 0x40059D: main (in /data/tmp/env/a.out)
>
> What I am trying to explain, you have something not
> defined in spec, was resolved in a way (you may not like, I agree)
> for EONs.
>
never worked
bsd always crashed
glibc used to generate invalid memory access which can lead to
arbitrarily bad behaviour, now it's fixed to crash
musl always crashed
> Now "you" decide, to resolve UB another way, you may
> have tons of applications in jeopardy.
>
next prev parent reply other threads:[~2015-04-23 14:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 0:08 Jean-Marc Pigeon
2015-04-23 0:35 ` Laurent Bercot
2015-04-23 1:26 ` Jean-Marc Pigeon
2015-04-23 2:15 ` Rich Felker
2015-04-23 4:24 ` Jean-Marc Pigeon
2015-04-23 5:08 ` Raphael Cohn
2015-04-23 12:29 ` Jean-Marc Pigeon
2015-04-23 9:23 ` Laurent Bercot
2015-04-23 9:52 ` Raphael Cohn
2015-04-23 10:47 ` Laurent Bercot
2015-04-23 10:10 ` Rich Felker
2015-04-23 12:58 ` Jean-Marc Pigeon
2015-04-23 13:22 ` Szabolcs Nagy
2015-04-23 13:58 ` Jean-Marc Pigeon
2015-04-23 14:26 ` Szabolcs Nagy [this message]
2015-04-23 8:05 ` Jens Gustedt
2015-04-23 9:55 ` Rich Felker
2015-04-24 4:11 ` Isaac Dunham
2015-04-23 5:52 ` Isaac Dunham
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=20150423142616.GA17440@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).