public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Godmar Back <godmar@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/2] posix: Add terminal control setting support for posix_spawn
Date: Mon, 28 Jun 2021 18:17:37 -0400	[thread overview]
Message-ID: <CAB4+JYJuAoUgmb6SEGfgL-yDu3dPZR+Dqbm4=1pbKc2Gfo4Heg@mail.gmail.com> (raw)
In-Reply-To: <8552a710-3ae4-8cf2-28a2-cd6dced45abf@linaro.org>

On Mon, Jun 28, 2021 at 6:03 PM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
>
>
> So there is no SIGTTOU being generated.  I even tried to add a timeout on
> the helper process to check if the problem is the signal being generated
> asynchronously, but it is works as intended.
>

I'm not familiar with the libc testing environment. When a process
runs in it, what is its controlling terminal? Is it part of a session?
Note that SIGTTOU is generated only if the process is part of a
session and if the terminal in question has a foreground process
group.

See https://github.com/torvalds/linux/blob/master/drivers/tty/tty_jobctrl.c#L49-L60

  reply	other threads:[~2021-06-28 22:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 17:57 [PATCH 1/2] posix: Remove spawni.c Adhemerval Zanella
2021-06-17 17:57 ` [PATCH 2/2] posix: Add terminal control setting support for posix_spawn Adhemerval Zanella
2021-06-17 18:15   ` Andreas Schwab
2021-06-28 20:10     ` Adhemerval Zanella
2021-06-28  1:11   ` Godmar Back
2021-06-28 22:03     ` Adhemerval Zanella
2021-06-28 22:17       ` Godmar Back [this message]
2021-06-29  8:12         ` Andreas Schwab
2021-06-29 17:03         ` Adhemerval Zanella
2021-06-29 19:35           ` Godmar Back
2021-06-28 22:01   ` Godmar Back

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='CAB4+JYJuAoUgmb6SEGfgL-yDu3dPZR+Dqbm4=1pbKc2Gfo4Heg@mail.gmail.com' \
    --to=godmar@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@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).