Debugging Rust on Windows with the GNU ABI

[Bamberghh]

I was having some problems with debugging Rust on the MSVC ABI (mainly the debugger being too slow and timing out) and I wanted to try the GNU ABI, as it's the recommended one (https://github.com/vadimcn/codelldb/wiki/Windows#debugging-rust-on-windows).

However when I build the executable with the GNU ABI (nightly-x86_64-pc-windows-gnu), the debugger complains in the debug console: warning: (x86_64) [executable].exe unable to locate separate debug file (dwo, dwp). Debugging will be degraded. and the enum values like Options aren't shown correctly.

And the problem is that I couldn't find a way to compile the project with the split debugging info on the GNU ABI - on MSVC the PDB is generated, but not on GNU, yes, with the [profile.dev] split-debuginfo = "packed" in the Cargo.toml. See also my question on the Rust forums for the details: https://users.rust-lang.org/t/building-split-debug-info-files-on-windows-with-the-gnu-abi/129511. What's then the intended way to debug on Windows?

Also on the GNU ABI the debugger doesn't catch panics and the program just exits without hitting the on panic breakpoint.

[vadimcn]

TBH, I haven't tried split debug info so far. The default for DWARF is a .debug_info section embedded in the binary, so I just use that.

Also on the GNU ABI the debugger doesn't catch panics and the program just exits without hitting the on panic breakpoint.

Yep, sounds like missing debug info.

[Bamberghh]

Yep, sounds like missing debug info.

But the breakpoints (not panics) are getting hit and the executable headers (gotten via dumpbin /headers [executable].exe) like .debug_info, .debug_line, etc. are present - the debug info is there.

However also enum values aren't shown correctly - they're shown either as those unreadable $variants$ fields (see picture below) or as error: invalid value object - unlike in the MSVC ABI where they're shown correctly like Some(123).

An enum value shown in the GNU ABI