Index | Thread | Search

From:
Claudio Jeker <cjeker@diehard.n-r-g.com>
Subject:
Re: changes to signal handling with respect to ksh ?
To:
Walter Alejandro Iglesias <wai@roquesor.com>
Cc:
"Todd C. Miller" <Todd.Miller@sudo.ws>, Theo Buehler <tb@theobuehler.org>, Marc Espie <marc.espie.openbsd@gmail.com>, ports@openbsd.org
Date:
Fri, 9 Aug 2024 10:20:33 +0200

Download raw body.

Thread
On Fri, Aug 09, 2024 at 08:18:55AM +0200, Walter Alejandro Iglesias wrote:
> On Thu, Aug 08, 2024 at 09:06:30PM +0200, Claudio Jeker wrote:
> > On Thu, Aug 08, 2024 at 09:31:47AM -0600, Todd C. Miller wrote:
> > > You might try changing that raise(SIGSTOP) in terminal_thread() to
> > > kill(getpid(), SIGSTOP).  You want to stop the entire process, not
> > > just the terminal thread.
> > > 
> > > Prior to that commit, each thread that received SIGTSTP would be
> > > stopped.  After the commit, only the terminal thread will be stopped.
> > 
> > In OpenBSD SIGSTOP is always process level. It will stop all threads but
> > the handling of SIGSTOP is currently subtly broken.
> 
> Can I conclude from this that mpv developers did nothing wrong?  Should
> I let them know about this and close the issue I opened in github?

No. It could be but it may as well be something else.
Is it enough to play a movie in mpv and ^Z the thing to see the problem?

-- 
:wq Claudio