Alan Wu b5fa156b79 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] (cherry picked from commit b385f7670f)		2020-03-30 19:15:11 +09:00
..
arith_seq
array
bignum
bug_reporter
class
debug
exception
file
float
funcall	Reword keyword arguments warning messages to convey these are deprecation warnings	2019-12-23 16:47:33 -05:00
gvl
hash
integer
iseq_load
iter
load
marshal	Warn instance variable E	2019-08-10 13:18:41 +09:00
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
st
string	test/-ext-/string/test_fstring.rb: suppress a warning for taint	2019-11-18 09:25:49 -06: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-30 19:15:11 +09: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
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	Reword keyword arguments warning messages to convey these are deprecation warnings	2019-12-23 16:47:33 -05:00