diff options
author | ko1 <ko1@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2017-06-12 04:52:25 +0000 |
---|---|---|
committer | ko1 <ko1@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2017-06-12 04:52:25 +0000 |
commit | 6c3f1461cd8052486f8e124f8f899447f653505b (patch) | |
tree | f302d31ad61acb16aece3788f803559c771e3348 /signal.c | |
parent | a57d295e36980fe7667f5557c4741339d7684fdc (diff) |
remove ruby_kill() introduced for [Bug #7951].
* thread.c (rbuy_kill): removed. This function is used
with SIGSEGV, SIGBUS, SIGKILL, SIGILL, SIGFPE and SIGSTOP
and these signals are affect immediately. So that `kill(2)'
is enough for them.
* signal.c (rb_f_kill): ditto.
* vm_core.h (rb_thread_t::interrupt_cond): removed because
only `ruby_kill()' uses this field.
* test/ruby/test_signal.rb: Without this patch sending SIGSTOP to own
process wait another interrupt even if another process sends SIGCONT.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59066 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'signal.c')
-rw-r--r-- | signal.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -495,7 +495,7 @@ rb_f_kill(int argc, const VALUE *argv) #ifdef SIGSTOP case SIGSTOP: #endif - ruby_kill(pid, sig); + kill(pid, sig); break; default: t = signal_ignored(sig); |