mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
36da0b3da1
Asynchronous events such as signal trap, finalization timing, thread switching and so on are managed by "interrupt_flag". Ruby's threads check this flag periodically and if a thread does not check this flag, above events doesn't happen. This checking is CHECK_INTS() (related) macro and it is placed at some places (laeve instruction and so on). However, at the end of C methods, C blocks (IMEMO_IFUNC) etc there are no checking and it can introduce uninterruptible thread. To modify this situation, we decide to place CHECK_INTS() at vm_pop_frame(). It increases interrupt checking points. [Bug #16366] This patch can introduce unexpected events... |
||
|---|---|---|
| .. | ||
| backtrace/location | ||
| fixtures | ||
| shared | ||
| abort_on_exception_spec.rb | ||
| add_trace_func_spec.rb | ||
| alive_spec.rb | ||
| allocate_spec.rb | ||
| backtrace_locations_spec.rb | ||
| backtrace_spec.rb | ||
| current_spec.rb | ||
| element_reference_spec.rb | ||
| element_set_spec.rb | ||
| exclusive_spec.rb | ||
| exit_spec.rb | ||
| fetch_spec.rb | ||
| fork_spec.rb | ||
| group_spec.rb | ||
| initialize_spec.rb | ||
| inspect_spec.rb | ||
| join_spec.rb | ||
| key_spec.rb | ||
| keys_spec.rb | ||
| kill_spec.rb | ||
| list_spec.rb | ||
| main_spec.rb | ||
| name_spec.rb | ||
| new_spec.rb | ||
| pass_spec.rb | ||
| priority_spec.rb | ||
| raise_spec.rb | ||
| report_on_exception_spec.rb | ||
| run_spec.rb | ||
| set_trace_func_spec.rb | ||
| start_spec.rb | ||
| status_spec.rb | ||
| stop_spec.rb | ||
| terminate_spec.rb | ||
| thread_variable_get_spec.rb | ||
| thread_variable_set_spec.rb | ||
| thread_variable_spec.rb | ||
| thread_variables_spec.rb | ||
| value_spec.rb | ||
| wakeup_spec.rb | ||