public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pb at pbcl dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18433] posix_spawn does not return correctly upon failure to execute
Date: Thu, 10 Sep 2015 18:20:00 -0000	[thread overview]
Message-ID: <bug-18433-131-6bnxgouNek@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18433-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18433

Phil Blundell <pb at pbcl dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pb at pbcl dot net

--- Comment #2 from Phil Blundell <pb at pbcl dot net> ---
The standard does not seem to specifically require this situation to be
diagnosed in the way you suggest.  In particular, it permits;

If [an] error occurs after the calling process successfully returns from the
posix_spawn() or posix_spawnp() function, the child process may exit with exit
status 127.

and notes:

A library implementation of posix_spawn() or posix_spawnp() may not be able to
detect all possible errors before it forks the child process. POSIX.1-2008
provides for an error indication returned from a child process which could not
successfully complete the spawn operation via a special exit status which may
be detected using the status value returned by wait(), waitid(), and waitpid().

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-09-10 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 20:34 [Bug libc/18433] New: " nachms+sourceware at gmail dot com
2015-06-05  9:41 ` [Bug libc/18433] " fweimer at redhat dot com
2015-09-10 14:25 ` rahimi.nv at gmail dot com
2015-09-10 18:20 ` pb at pbcl dot net [this message]
2015-09-12 19:03 ` nachms+sourceware at gmail dot com
2015-09-12 20:56 ` rahimi.nv at gmail dot com
2015-09-12 21:00 ` rahimi.nv at gmail dot com
2015-09-12 21:07 ` rahimi.nv at gmail dot com
2015-09-13 12:15 ` rahimi.nv at gmail dot com
2021-07-26 19:03 ` vtjnash at gmail dot com
2021-07-26 19:33 ` adhemerval.zanella at linaro dot org

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=bug-18433-131-6bnxgouNek@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).