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/extract
array/resize
bignum
bug-3571
bug-5832
bug-14834
bug_reporter
class
cxxanyargs	The last argument of rb_rescue2() should always be (VALUE)0	2020-03-28 13:03:17 +01:00
debug
dln/empty
enumerator_kw
exception
fatal
file
float
funcall
gvl/call_without_gvl
hash
integer
iseq_load
iter
load
marshal
memory_status
method
notimplement
num2int
path_to_class
popen_deadlock	Fix linkage of popen_deadlock test	2020-02-04 08:04:13 +09:00
postponed_job
printf
proc
rational
rb_call_super_kw
recursion
regexp
scan_args
st
string
struct
symbol
thread_fd_close
time
tracepoint	Clear all trace events during teardown	2020-03-29 23:41:19 -04:00
typeddata	more on NULL versus functions.	2020-02-07 14:24:19 +09:00
vm
wait_for_single_fd
win32
auto_ext.rb