From e41fde8b776e299342543a85f315646a25bec194 Mon Sep 17 00:00:00 2001 From: nobu Date: Sun, 21 Sep 2014 02:03:34 +0000 Subject: signal.c: EINVAL is a failure * signal.c (ruby_signal): although "EINVAL from sigaction(2) is not a bug", but even it is a failure. pointed at toRuby/guRuby in RubyHiroba. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@47657 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- test/ruby/test_signal.rb | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'test/ruby') diff --git a/test/ruby/test_signal.rb b/test/ruby/test_signal.rb index 251a12db17..e4cca022b3 100644 --- a/test/ruby/test_signal.rb +++ b/test/ruby/test_signal.rb @@ -169,6 +169,14 @@ class TestSignal < Test::Unit::TestCase end end if Process.respond_to?(:kill) + %w"KILL STOP".each do |sig| + if Signal.list.key?(sig) + define_method("test_trap_uncatchable_#{sig}") do + assert_raise(Errno::EINVAL, "SIG#{sig} is not allowed to be caught") { Signal.trap(sig) {} } + end + end + end + def test_kill_immediately_before_termination Signal.list[sig = "USR1"] or sig = "INT" assert_in_out_err(["-e", <<-"end;"], "", %w"foo") -- cgit v1.2.3