chore: use tracing-panic to better capture panic info

libnyanpasu · Jul 20, 2024 · 4616f17 · 4616f17
1 parent 3c81d4c
commit 4616f17
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 11 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/nyanpasu_service/Cargo.toml b/nyanpasu_service/Cargo.toml
@@ -38,6 +38,7 @@ tracing-subscriber = { workspace = true, features = [
     "parking_lot",
 ] }
 tracing-attributes.workspace = true
+tracing-panic = "0.1"
 service-manager = { git = "https://github.com/greenhat616/service-manager-rs.git" }
 parking_lot = "0.12"
 constcat = "0.5.0"

diff --git a/nyanpasu_service/src/utils/mod.rs b/nyanpasu_service/src/utils/mod.rs
@@ -1,5 +1,6 @@
 use anyhow::Context;
 use service_manager::ServiceManager;
+use tracing_panic::panic_hook;
 
 pub mod dirs;
 pub mod os;
@@ -56,15 +57,5 @@ pub fn deadlock_detection() {
 
 /// Register a panic hook to log the panic message and location, then exit the process.
 pub fn register_panic_hook() {
-    std::panic::set_hook(Box::new(|panic_info| {
-        let location = panic_info.location().unwrap();
-        let message = panic_info.payload().downcast_ref::<&str>().unwrap();
-        tracing::error!(
-            "panic occurred at {}:{}: {}",
-            location.file(),
-            location.line(),
-            message
-        );
-        std::process::exit(1);
-    }));
+    std::panic::set_hook(Box::new(panic_hook));
 }