stage1 compiler has some debuginfo with misleading library paths #142050
Labels
A-contributor-roadblock
Area: Makes things more difficult for new or seasoned contributors to Rust
A-dist-components
Area: dist components, e.g. `rustc-dev`, `rustc-src`, etc.
A-path-remapping
Area: path remapping, --remap-path-prefix, --remap-cwd-prefix, --remap-diagnostics-scope etc.
C-bug
Category: This is a bug.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
I tried debugging
stage1/bin/rustc
, and when stepping into parts of the standard library, I noticed that gdb was showing file contents from the locallibrary/
path, even though thestage1
compiler is now built withstage0
's standard library.While a lot of the library paths are
/rust/{hash}/...
prefixed, some are still relative, and the debugger dutifully opens the local file that doesn't actually match.In this brief example, it doesn't really matter because
time.rs
hasn't changed, but in deeper debugging sessions I saw completely bogus lines, like in the middle of a large comment block. I can make a local edit on this file and gdb will still show that next time:When the stage0 library path is properly remapped, it looks more like this:
(We could potentially find that file with
rust-src
andrust-gdb
matching the stage0 compiler.)Meta
Tried on
master
as of commit61413aea937d9663d01b62902535f8d4ec85cc95
.The text was updated successfully, but these errors were encountered: