public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25715] system() returns wrong errors when posix_spawn fails
Date: Tue, 24 Mar 2020 12:16:31 +0000 [thread overview]
Message-ID: <bug-25715-131-luODaVb8yQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25715-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25715
--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.31/master branch has been updated by Adhemerval Zanella
<azanella@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=46bbbd4622351528ae22c2d3397ab090f5099e82
commit 46bbbd4622351528ae22c2d3397ab090f5099e82
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date: Mon Mar 23 15:23:20 2020 -0300
posix: Fix system error return value [BZ #25715]
It fixes 5fb7fc9635 when posix_spawn fails.
Checked on x86_64-linux-gnu and i686-linux-gnu.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
(cheery picked from commit f09542c584b121da0322fde4b55306d512b85d93)
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-03-24 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 13:48 [Bug libc/25715] New: " pokogiv215 at sweatmail dot com
2020-03-23 14:01 ` [Bug libc/25715] " adhemerval.zanella at linaro dot org
2020-03-23 16:24 ` adhemerval.zanella at linaro dot org
2020-03-23 21:05 ` cvs-commit at gcc dot gnu.org
2020-03-23 21:06 ` adhemerval.zanella at linaro dot org
2020-03-24 11:51 ` cvs-commit at gcc dot gnu.org
2020-03-24 12:16 ` cvs-commit at gcc dot gnu.org [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=bug-25715-131-luODaVb8yQ@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).