summaryrefslogtreecommitdiff
path: root/ext/-test-
diff options
context:
space:
mode:
authorAlan Wu <XrXr@users.noreply.github.com>2020-03-11 10:37:14 -0400
committerAlan Wu <XrXr@users.noreply.github.com>2020-03-29 23:41:19 -0400
commitb385f7670ffa420790bc548747fa4b58c4c5d8f6 (patch)
tree43d129066268a271ba22271253c2dedc2e8335f7 /ext/-test-
parent2a3f45bdb39c750e6f55525151cf3f9a5d727617 (diff)
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]
Notes
Notes: Merged: https://github.com/ruby/ruby/pull/2959
Diffstat (limited to 'ext/-test-')
-rw-r--r--ext/-test-/tracepoint/gc_hook.c8
1 files changed, 8 insertions, 0 deletions
diff --git a/ext/-test-/tracepoint/gc_hook.c b/ext/-test-/tracepoint/gc_hook.c
index 2e695a9fbad..54b469dcad6 100644
--- a/ext/-test-/tracepoint/gc_hook.c
+++ b/ext/-test-/tracepoint/gc_hook.c
@@ -73,8 +73,16 @@ set_after_gc_start(VALUE module, VALUE proc)
"__set_after_gc_start_tpval__", "__set_after_gc_start_proc__");
}
+static VALUE
+start_after_gc_exit(VALUE module, VALUE proc)
+{
+ return set_gc_hook(module, proc, RUBY_INTERNAL_EVENT_GC_EXIT,
+ "__set_after_gc_exit_tpval__", "__set_after_gc_exit_proc__");
+}
+
void
Init_gc_hook(VALUE module)
{
rb_define_module_function(module, "after_gc_start_hook=", set_after_gc_start, 1);
+ rb_define_module_function(module, "after_gc_exit_hook=", start_after_gc_exit, 1);
}