From: xtkoba+ruby@... Date: 2021-04-22T20:46:32+00:00 Subject: [ruby-core:103562] [Ruby master Bug#17820] `Errno::EINVAL` from `Process.kill` with available signal on Windows Issue #17820 has been updated by xtkoba (Tee KOBAYASHI). The signals (except for `EXIT`, that is a pseudo signal) listed in `Signal.list` are valid to be sent to `Process.pid` (`$$`). I suppose it is not easy to make POSIX signals consistent with Windows. ---------------------------------------- Bug #17820: `Errno::EINVAL` from `Process.kill` with available signal on Windows https://bugs.ruby-lang.org/issues/17820#change-91663 * 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: