diff options
author | Yusuke Endoh <[email protected]> | 2019-10-09 23:02:22 +0900 |
---|---|---|
committer | Yusuke Endoh <[email protected]> | 2019-10-09 23:02:22 +0900 |
commit | dd477df411691803fc5a83c7daa64faac112a0e4 (patch) | |
tree | 0a95c5ef1206fee0e4340ffe07f932034943c298 /signal.c | |
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 'signal.c')
-rw-r--r-- | signal.c | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -933,7 +933,7 @@ sigbus(int sig SIGINFO_ARG) #if defined __APPLE__ || defined __linux__ CHECK_STACK_OVERFLOW(); #endif - rb_bug_context(SIGINFO_CTX, "Bus Error" MESSAGE_FAULT_ADDRESS); + rb_bug_for_fatal_signal(SIGINFO_CTX, "Bus Error" MESSAGE_FAULT_ADDRESS); } #endif @@ -946,7 +946,7 @@ sigsegv(int sig SIGINFO_ARG) { check_reserved_signal("SEGV"); CHECK_STACK_OVERFLOW(); - rb_bug_context(SIGINFO_CTX, "Segmentation fault" MESSAGE_FAULT_ADDRESS); + rb_bug_for_fatal_signal(SIGINFO_CTX, "Segmentation fault" MESSAGE_FAULT_ADDRESS); } #endif @@ -961,7 +961,7 @@ sigill(int sig SIGINFO_ARG) #if defined __APPLE__ CHECK_STACK_OVERFLOW(); #endif - rb_bug_context(SIGINFO_CTX, "Illegal instruction" MESSAGE_FAULT_ADDRESS); + rb_bug_for_fatal_signal(SIGINFO_CTX, "Illegal instruction" MESSAGE_FAULT_ADDRESS); } #endif |