public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vtjnash at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/18433] posix_spawn does not return correctly upon failure to execute Date: Mon, 26 Jul 2021 19:03:58 +0000 [thread overview] Message-ID: <bug-18433-131-iBDFPVzw01@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18433-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18433 Jameson <vtjnash at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vtjnash at gmail dot com --- Comment #10 from Jameson <vtjnash at gmail dot com> --- Sorry to ping an old issue, but I was noticing the documentation appears to explicitly state the old behavior (https://man7.org/linux/man-pages/man3/posix_spawn.3.html#ERRORS), in contradiction to this change and the updated opengroups standard at the link in the original issue or at https://linux.die.net/man/3/posix_spawn. Is this text now incorrect: ERRORS The posix_spawn() and posix_spawnp() functions fail only in the case where the underlying fork(2) or vfork(2) call fails; in these cases, these functions return an error number, which will be one of the errors described for fork(2) or vfork(2). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-26 19:03 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 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 [this message] 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-iBDFPVzw01@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: linkBe 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).