[ruby-core:107105] [Ruby master Bug#18444] Trapped TSTP causes a locking deadlock in 3.0.3 onward

Issue #18444 has been updated by jeremyevans0 (Jeremy Evans).


I couldn't replicate this behavior in OpenBSD/amd64.  On OpenBSD/amd64, sending TSTP prints the Received... string twice, 10 seconds part, followed by the loop printing 1.  Windows doesn't support TSTP, so no reason to test there.  Can anyone replicate this outside of M1 MacOS?


----------------------------------------
Bug #18444: Trapped TSTP causes a locking deadlock in 3.0.3 onward
https://bugs.ruby-lang.org/issues/18444#change-95951

* Author: why-el (Mohamed Wael Khobalatte)
* Status: Open
* Priority: Normal
* ruby -v: 3.0.3
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
A curious case: 

`ruby -e 'Signal.trap("TSTP") { puts "Received a terminal stop signal, but i will sleep instead."; sleep 10 }; loop {puts 1}'`

this fails with `deadlock; recursive locking (ThreadError)` when I send the SIGTSTP via my terminal. This is on Mac OS Monterey (M1). It only happens in 3.0.3 and onward (I tried 3.1.0-preview1 as well, fails there too), when I try 3.0.2, the signal is handled properly.





-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>