diff options
| author | Yusuke Endoh <mame@ruby-lang.org> | 2019-10-09 23:02:22 +0900 |
|---|---|---|
| committer | Yusuke Endoh <mame@ruby-lang.org> | 2019-10-09 23:02:22 +0900 |
| commit | dd477df411691803fc5a83c7daa64faac112a0e4 (patch) | |
| tree | 0a95c5ef1206fee0e4340ffe07f932034943c298 /vm_core.h | |
| parent | b9cf58d2b2deca7d5b204080c2fe04d68cc50ab1 (diff) | |
error.c (rb_bug_for_fatal_signal): renamed from rb_bug_context
Just refactoring.
The name "rb_bug_context" is completely unclear for me.
(Can you see that "context" means "machine register context"?)
The context is available only when a fatal signal (sigbus, sigsegv, or
sigill) is received; in fact, the function is used only for fatal
signals. So, I think the name should be changed.
Diffstat (limited to 'vm_core.h')
| -rw-r--r-- | vm_core.h | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1624,7 +1624,7 @@ extern void rb_vmdebug_debug_print_post(const rb_execution_context_t *ec, const #define SDR() rb_vmdebug_stack_dump_raw(GET_EC(), GET_EC()->cfp) #define SDR2(cfp) rb_vmdebug_stack_dump_raw(GET_EC(), (cfp)) void rb_vm_bugreport(const void *); -NORETURN(void rb_bug_context(const void *, const char *fmt, ...)); +NORETURN(void rb_bug_for_fatal_signal(const void *, const char *fmt, ...)); /* functions about thread/vm execution */ RUBY_SYMBOL_EXPORT_BEGIN |