是否可以在不惊慌的情况下在 Rust 中打印回溯? [英] Is it possible to print a backtrace in Rust without panicking?

查看:85
本文介绍了是否可以在不惊慌的情况下在 Rust 中打印回溯?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是否可以在不惊慌的情况下打印回溯(假设启用了 RUST_BACKTRACE)?似乎唯一的方法是通过 panic! 调用.如果不是,有什么原因吗?

Is it possible to print a backtrace (assuming RUST_BACKTRACE is enabled) without panicking? It seems that the only way of doing that is calling via panic!. If not, is there a reason for it?

推荐答案

Rust 使用 backtrace crate 来在发生恐慌时打印回溯(已在 PR #60852 中合并).

Rust uses the backtrace crate to print the backtrace in case of panics (has been merged in PR #60852).

一个简单的例子可以在 crate 文档中找到

A simple example can be found in the crate documentation

use backtrace::Backtrace;

fn main() {
    let bt = Backtrace::new();

    // do_some_work();

    println!("{:?}", bt);
}

举个例子

stack backtrace:
   0: playground::main::h6849180917e9510b (0x55baf1676201)
             at src/main.rs:4
   1: std::rt::lang_start::{{closure}}::hb3ceb20351fe39ee (0x55baf1675faf)
             at /rustc/3c235d5600393dfe6c36eeed34042efad8d4f26e/src/libstd/rt.rs:64
   2: {{closure}} (0x55baf16be492)
             at src/libstd/rt.rs:49
      do_call<closure,i32>
             at src/libstd/panicking.rs:293
   3: __rust_maybe_catch_panic (0x55baf16c00b9)
             at src/libpanic_unwind/lib.rs:87
   4: try<i32,closure> (0x55baf16bef9c)
             at src/libstd/panicking.rs:272
      catch_unwind<closure,i32>
             at src/libstd/panic.rs:388
      lang_start_internal
             at src/libstd/rt.rs:48
   5: std::rt::lang_start::h2c4217f9057b6ddb (0x55baf1675f88)
             at /rustc/3c235d5600393dfe6c36eeed34042efad8d4f26e/src/libstd/rt.rs:64
   6: main (0x55baf16762f9)
   7: __libc_start_main (0x7fab051b9b96)
   8: _start (0x55baf1675e59)
   9: <unknown> (0x0)

这篇关于是否可以在不惊慌的情况下在 Rust 中打印回溯?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆