WinDbg does not understand niche-layout enums and the information provided is not very useful unless you understand how niche-layout works. Even then, aside from simple cases like the 0 niche for references, it can be non-trivial to decode what variant of the enum is active when either the niche is not 0 or the enum contains multiple tag only variants, not just one like Option does.
fn main() {
let x = Some(&1u32);
let y = Option::<&'static u32>::None;
std::process::exit(0); // bp here
}
Having the debuginfo more like the direct-tag layout case would help.
WinDbg does not understand niche-layout enums and the information provided is not very useful unless you understand how niche-layout works. Even then, aside from simple cases like the
0niche for references, it can be non-trivial to decode what variant of the enum is active when either the niche is not 0 or the enum contains multiple tag only variants, not just one likeOptiondoes.Having the debuginfo more like the direct-tag layout case would help.