public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28853] Problems with terminal control Date: Wed, 02 Feb 2022 18:04:43 +0000 [thread overview] Message-ID: <bug-28853-131-K3w0PWukOm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28853-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28853 --- Comment #2 from John David Anglin <danglin at gcc dot gnu.org> --- I suppose this is the problematic part of the change: /* Set the controlling terminal. */ if ((attr->__flags & POSIX_SPAWN_TCSETPGROUP) != 0) { /* Check if it is possible to avoid an extra syscall. */ pid_t pgrp = (attr->__flags & POSIX_SPAWN_SETPGROUP) != 0 && attr->__pgrp != 0 ? attr->__pgrp : __getpgid (0); if (__tcsetpgrp (attr->__ctty_fd, pgrp) != 0) goto fail; } -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-02 18:04 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-02 16:37 [Bug libc/28853] New: " danglin at gcc dot gnu.org 2022-02-02 17:15 ` [Bug libc/28853] " schwab@linux-m68k.org 2022-02-02 18:04 ` danglin at gcc dot gnu.org [this message] 2022-02-02 18:08 ` danglin at gcc dot gnu.org 2022-02-02 19:35 ` carlos at redhat dot com 2022-02-02 19:35 ` [Bug libc/28853] tst-spawn6 changes current foreground process group (breaks test isolation) carlos at redhat dot com 2022-02-02 19:37 ` carlos at redhat dot com 2022-02-03 1:22 ` sam at gentoo dot org 2022-02-03 4:09 ` carlos at redhat dot com 2022-02-03 11:10 ` adhemerval.zanella at linaro dot org 2022-02-03 11:11 ` adhemerval.zanella at linaro dot org 2022-02-03 11:13 ` adhemerval.zanella at linaro dot org 2022-02-07 16:40 ` 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-28853-131-K3w0PWukOm@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).