Bug: didn't catch panics

[Banyc]

rust-analyzer version: 0.3.1140-standalone (7e2b983 2022-07-24)

rustc version: rustc 1.62.1 (e092d0b6b 2022-07-16)

relevant settings: (eg. client settings, or environment variables like CARGO, RUSTUP_HOME or CARGO_HOME)

When panicking, the debug session exited without catching the source of panic. But the breakpoint is still working fine. It is on VSCode.

[lnicola]

We don't have any support for debugging except pointing your debugging extension (CodeLLDB, Native Debug) in the right direction. Those extensions may or may not have support for catching exceptions when they are thrown.

[lnicola]

In CodeLLDB it's these ones, but they don't work for me either:

Acutally, it doesn't work at all: rust-lang/rust#21102.

[Banyc]

@lnicola I have crossposted it to CodeLLDB, and hope this issue can be settled

[lnicola]

It's not actually CodeLLDB either, since neither lldb, nor rust-lldb work. You might need to put breakpoints on rust_panic and rust_begin_unwind instead.

[Banyc]

@lnicola This issue only happens recently, not a problem before, so I think there is a newly introduced bug somewhere.

[lnicola]

Ah, then maybe try compiling with an older Rust version.

[Banyc]

Solution

add the rust_panic breakpoint