From: alex.wayfer@... Date: 2021-04-22T20:19:23+00:00 Subject: [ruby-core:103560] [Ruby master Bug#17820] `Errno::EINVAL` from `Process.kill` with available signal on Windows Issue #17820 has been updated by AlexWayfer (Alexander Popov). File clipboard-202104222318-tbufr.png added Also I found a very strange behavior with `Signal.trap`, not sure is it related, but I'm still sure that all signals should be synchronized and consistent. So��� `Signal.trap('KILL')` raises `Invalid argument - SIGKILL (Errno::EINVAL)`. And other signals, which are incorrect for `Process.kill`, don't raise errors: ![](clipboard-202104222318-tbufr.png) ---------------------------------------- Bug #17820: `Errno::EINVAL` from `Process.kill` with available signal on Windows https://bugs.ruby-lang.org/issues/17820#change-91661 * Author: AlexWayfer (Alexander Popov) * Status: Open * Priority: Normal * ruby -v: ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x64-mingw32] * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- Hello. I've installed Ruby on Windows via [Chocolatey](https://community.chocolatey.org/packages/ruby). I receive `Errno::EINVAL` from `Process.kill` with almost every signal. Only `0` seems working. `TERM` (`15`), `INT` (`2`) ��� don't. Although they're in `Signal.list` output: ![](clipboard-202104222051-b64xq.png) ---Files-------------------------------- clipboard-202104222051-b64xq.png (63.9 KB) clipboard-202104222318-tbufr.png (96.8 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: