From: Mike Frysinger <vapier@gentoo.org>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: When is it OK to pass NULLs to the 2nd and 3rd args of execve()?
Date: Fri, 9 Apr 2021 18:06:37 -0400 [thread overview]
Message-ID: <YHDP7aGEYAKHe7UC@vapier> (raw)
In-Reply-To: <CABrM6wkYV4qn0V=7j5FPD8jB9Dn2M+fjQHJHrEpvnqJ4aA_riQ@mail.gmail.com>
On 09 Apr 2021 11:53, Peng Yu via Libc-help wrote:
> I am wondering when (all possible legitimate cases) it is OK to pass
> NULLs to execve's 2nd and 3rd args.
>
> #include <unistd.h>
> #include <stdio.h>
>
> int main(int argc, char *argv[]) {
> if(execve(argv[1], NULL, NULL) == -1) {
> perror("execvp()");
> return 1;
> }
> return 0;
> }
>
>
> I tried the above program. It works when it is called with `/bin/sh`.
> My guess is that when the program being exec'ed don't use its args and
> envs, then then 2nd and 3rd args of execve() can be NULLs. Could
> anybody correct me if I am wrong?
never do this. POSIX doesn't allow it, and no programs account for it.
if you were try to report it as such, you'd (rightly) be told no.
i recall coreutils for example segfaults when it tries to deref argv[0].
https://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html
-mike
prev parent reply other threads:[~2021-04-09 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 16:53 Peng Yu
2021-04-09 17:03 ` tomas
2021-04-09 17:20 ` Peng Yu
2021-04-09 17:32 ` tomas
2021-04-09 22:06 ` Mike Frysinger [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=YHDP7aGEYAKHe7UC@vapier \
--to=vapier@gentoo.org \
--cc=libc-help@sourceware.org \
--cc=pengyu.ut@gmail.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).