You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking into this mostly because I have no idea how any of this works. I found two crates that seem to produce pdb files (bao-pdb, pdb_wrapper), but I'm not sure how complete they are or if they work for our use case.
A more interesting approach is what LLVM does for generating CodeView. LLVM apparently only emits CodeView line tables, and DWARF debug info (which we already know how to do!) And lets link.exe convert it into a PDB file, this seems like a much easier solution and maybe implementing only that part of CodeView would be easier.
cg_clif already only supports line information anyway. I couldn't quite get the Cranelift integration for value tracking working reliably last time I tried.
It looks like cg_clif doesn't support debug info on Windows. It would be nice if we could do that!
Some pdb files are generated but I'm not sure what's in them (see: https://github.com/bjorn3/rustc_codegen_cranelift/issues/1249#issuecomment-1262034841).
I've been looking into this mostly because I have no idea how any of this works. I found two crates that seem to produce pdb files (bao-pdb, pdb_wrapper), but I'm not sure how complete they are or if they work for our use case.
A more interesting approach is what LLVM does for generating CodeView. LLVM apparently only emits CodeView line tables, and DWARF debug info (which we already know how to do!) And lets
link.exe
convert it into a PDB file, this seems like a much easier solution and maybe implementing only that part of CodeView would be easier.Edit: Re-reading the rust issue, it looks like this doesn't get us variable and type information, only line information.
Edit 2: That information is also out of date, LLVM now has full CodeView support, but its good to know that that's how they started out.
Additional links:
The text was updated successfully, but these errors were encountered: