From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: Cannot exec() program outside of /bin if PATH is unset
Date: Sun, 14 Sep 2014 09:40:00 -0000 [thread overview]
Message-ID: <CAEhDDbAk8iSeG6CaSDBY8o-DLUUd+xJaATDbP=rBG9qUfFLe+A@mail.gmail.com> (raw)
In-Reply-To: <54134A83.80107@redhat.com>
On Fri, Sep 12, 2014 at 9:33 PM, Eric Blake wrote:
> On 09/12/2014 11:02 AM, Christian Franke wrote:
(snip)
>>
>> int main()
>> {
>> unsetenv("PATH");
>
> This is undefined behavior, per POSIX. POSIX recommends that you always
> leave PATH defined to at least a bare minimum of the results of
> confstr(_CS_PATH, ...); it also states that implementations are free to
> do what they want (in this case, crash) if you don't follow the
> recommendation:
>
> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
> "If PATH is unset or is set to null, the path search is
> implementation-defined."
Nitpick: undefined != implementation-defined
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2014-09-14 9:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 18:02 Christian Franke
2014-09-12 19:39 ` Eric Blake
2014-09-12 21:14 ` Christian Franke
2014-09-12 21:56 ` Andrey Repin
2014-09-12 23:04 ` Christian Franke
2014-09-12 23:06 ` Eric Blake
2014-09-12 23:13 ` Eric Blake
2014-09-13 16:17 ` Christian Franke
2014-09-15 7:47 ` Peter Rosin
2014-09-15 9:28 ` Peter Rosin
2014-09-15 17:16 ` Christian Franke
2014-10-08 13:41 ` Corinna Vinschen
2014-10-08 17:16 ` Christian Franke
2014-10-09 10:03 ` Corinna Vinschen
2014-10-09 14:25 ` Eric Blake
2014-10-09 16:29 ` Corinna Vinschen
2014-10-09 16:34 ` tednolan
2014-10-10 10:34 ` Corinna Vinschen
2014-10-10 11:24 ` Jan Nijtmans
2014-10-10 11:32 ` Arjen Markus
2014-10-10 12:10 ` tednolan
2014-10-10 12:13 ` Arjen Markus
2014-10-10 15:39 ` Corinna Vinschen
2014-10-14 19:30 ` Corinna Vinschen
2014-10-16 21:51 ` Christian Franke
2014-10-17 9:10 ` Corinna Vinschen
2014-10-17 14:51 ` Corinna Vinschen
2014-10-17 17:56 ` Christian Franke
2014-10-17 18:20 ` Corinna Vinschen
2014-10-17 20:36 ` Csaba Raduly
2014-09-12 22:50 ` Eric Blake
2014-09-13 5:24 ` David Boyce
2014-09-14 9:40 ` Csaba Raduly [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='CAEhDDbAk8iSeG6CaSDBY8o-DLUUd+xJaATDbP=rBG9qUfFLe+A@mail.gmail.com' \
--to=rcsaba@gmail.com \
--cc=cygwin@cygwin.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).