chore(base): rollback to kernel signal handler after dump backtrace

[zhang2014]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

chore(base): rollback to kernel signal handler after dump backtrace

• add SIGABRT handler for catch std::process::abort()
• avoid using head memory in signal handler
• rollback to kernel default signal handler after dump backtrace

Suggestions from: @dantengsky

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[dantengsky]

maybe we could use SA_RESETHAND (and keep the signal_handler as it is, but the exit(1) should be removed), something like this:

-- diff is based on this PR

diff --git a/src/common/tracing/src/crash_hook.rs b/src/common/tracing/src/crash_hook.rs
index 8596d78576..5264d74424 100644
--- a/src/common/tracing/src/crash_hook.rs
+++ b/src/common/tracing/src/crash_hook.rs
@@ -254,20 +254,16 @@ unsafe extern "C" fn signal_handler(sig: i32, info: *mut libc::siginfo_t, uc: *m

     #[allow(unreachable_code)]
     if sig != libc::SIGTRAP {
-        match libc::SIG_ERR == libc::signal(sig, libc::SIG_DFL) {
-            true => std::process::exit(1),
-            false => match libc::raise(sig) {
-                0 => {}
-                _ => std::process::exit(1),
-            },
-        }
+        drop(guard);
+        let _ = std::io::stderr().flush();
     }
 }

 pub unsafe fn add_signal_handler(signals: Vec<i32>) {
     let mut sa = std::mem::zeroed::<libc::sigaction>();

-    sa.sa_flags = libc::SA_ONSTACK | libc::SA_SIGINFO;
+    sa.sa_flags = libc::SA_ONSTACK | libc::SA_SIGINFO | libc::SA_RESETHAND;
     sa.sa_sigaction = signal_handler as usize;

     libc::sigemptyset(&mut sa.sa_mask);

and tweak sa_flags later, when the the mechanism of dumping backtrace is stabilized (currently, the dumping thread may have no opportunity to receive and dump all the trace from pipe, IMHO)

update: std::process::exit(1) should be removed, let the default handler (which is reset to by using SA_RESETHAND) exit the process. the whole point is to ensure coredump could be generated (if backtrace could not be captured)

[zhang2014]

refactored the signal handler to avoid using heap memory. please review it again.