This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/18433] posix_spawn does not return correctly upon failure to execute


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]