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/29109] posix_spawn() always returns 1 (EPERM) on clone() failure Date: Fri, 06 May 2022 14:34:32 +0000 [thread overview] Message-ID: <bug-29109-131-mhnxVljL8R@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29109-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29109 --- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.35/master branch has been updated by Adhemerval Zanella <azanella@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=bbb017a2bb2983de297f3d443c59221fbff92e30 commit bbb017a2bb2983de297f3d443c59221fbff92e30 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Fri May 6 11:34:18 2022 -0300 NEWS: Add a bug fix entry for BZ #29109 -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-05-06 14:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-01 14:52 [Bug libc/29109] New: " izbyshev at ispras dot ru 2022-05-01 14:53 ` [Bug libc/29109] " izbyshev at ispras dot ru 2022-05-01 23:30 ` adhemerval.zanella at linaro dot org 2022-05-02 13:21 ` fweimer at redhat dot com 2022-05-02 13:30 ` adhemerval.zanella at linaro dot org 2022-05-02 13:39 ` izbyshev at ispras dot ru 2022-05-02 13:46 ` adhemerval.zanella at linaro dot org 2022-05-06 14:09 ` adhemerval.zanella at linaro dot org 2022-05-06 14:34 ` 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-29109-131-mhnxVljL8R@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).