diff options
| author | Alan Wu <XrXr@users.noreply.github.com> | 2020-03-11 10:37:14 -0400 |
|---|---|---|
| committer | NARUSE, Yui <naruse@airemix.jp> | 2020-03-30 19:15:11 +0900 |
| commit | b5fa156b7907b8ea1baf8b9f0cb6a66b0fecb3d4 (patch) | |
| tree | e2551a6cc79b035f1a74e82da2703822e4c08086 /vm_trace.c | |
| parent | 0057fe4063b57b445d6ffc893e442f362e3a19e0 (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]
(cherry picked from commit b385f7670ffa420790bc548747fa4b58c4c5d8f6)
Diffstat (limited to 'vm_trace.c')
| -rw-r--r-- | vm_trace.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/vm_trace.c b/vm_trace.c index 9a604814c6..241b929671 100644 --- a/vm_trace.c +++ b/vm_trace.c @@ -276,6 +276,12 @@ rb_ec_clear_current_thread_trace_func(const rb_execution_context_t *ec) rb_threadptr_remove_event_hook(ec, rb_ec_thread_ptr(ec), 0, Qundef); } +void +rb_ec_clear_all_trace_func(const rb_execution_context_t *ec) +{ + rb_threadptr_remove_event_hook(ec, MATCH_ANY_FILTER_TH, 0, Qundef); +} + /* invoke hooks */ static void |