Alan Wu b385f7670f Clear all trace events during teardown ... Since 0c2d81dada, not all trace events are cleared during VM teardown. This causes a crash when there is a tracepoint for `RUBY_INTERNAL_EVENT_GC_EXIT` active during teardown. The commit looks like a refactoring commit so I think this change was unintentional. [Bug #16682]		2020-03-29 23:41:19 -04:00
..
arith_seq
array
bignum
bug_reporter	skip SEGV test if RUBY_ON_BUG is specified	2020-02-13 04:20:22 +09:00
class
debug
exception
file
float
funcall	Update tests for full keyword argument separation	2020-01-02 18:40:45 -08:00
gvl
hash
integer
iseq_load
iter
load
marshal
method
num2int
path_to_class
popen_deadlock	Fixed misspellings	2019-12-20 09:32:42 +09:00
postponed_job	check interrupts at each frame pop timing.	2019-11-29 17:47:02 +09:00
proc
rational	rb_rational_raw: convert num and den by to_int	2020-01-17 10:57:51 +09:00
st
string	Word array instead of splitting	2020-03-08 17:39:22 +09:00
struct	Fix typos	2019-11-09 21:12:29 +09:00
symbol
thread_fd_close
time
tracepoint	Clear all trace events during teardown	2020-03-29 23:41:19 -04:00
typeddata
vm
wait_for_single_fd
win32
test_bug-3571.rb
test_bug-5832.rb
test_bug-14834.rb
test_enumerator_kw.rb	Add rb_enumeratorize_with_size_kw and related macros	2019-09-30 07:06:42 -07:00
test_notimplement.rb	Moved not-implemented method tests [Bug #16662]	2020-02-28 21:15:37 +09:00
test_printf.rb	Deprecate taint/trust and related methods, and make the methods no-ops	2019-11-18 01:00:25 +02:00
test_recursion.rb
test_scan_args.rb	Update tests for full keyword argument separation	2020-01-02 18:40:45 -08:00