Can't step into libstd with gdb on Windows

[elahn]

fn main() {
    let mut input = String::new();

When I try to step in, I get:
Source C:\bot\slave\nightly-dist-rustc-win-gnu-64\build\obj\../src/libcollections/string.rs is not available.

When I set a breakpoint in string.rs and start a debug session, I get the error:
No source file named d:\dev\gnu\rust\src\libcollections\string.rs.
Note: this does not mean the file doesn't exist on the filesystem, it means it's not in the debug binary.

Workaround:

Set RUST_SRC_PATH=C:\bot\slave\nightly-dist-rustc-win-gnu-64\build\src

Either:

• Copy/move rust source code to C:\bot\slave\nightly-dist-rustc-win-gnu-64\build\src
• Or, as administrator:

C:\bot\slave\nightly-dist-rustc-win-gnu-64>mklink build C:\Users\Elahn\.multirust\toolchains\nightly-x86_64-pc-windows-gnu\lib\rustlib
symbolic link created for build <<===>> C:\Users\Elahn\.multirust\toolchains\nightly-x86_64-pc-windows-gnu\lib\rustlib

[elahn]

I've edited the issue: my local build wasn't being used because cargo.exe didn't exist in [build-dir]\bin

So, the issue is: debug info (source filename/location) is being generated when rust is built, but isn't being updated when linking libstd into the target binary.

[michaelwoerister]

Interesting. Thanks for the report!

[retep998]

If you use VS Code as your debugger you can use https://blogs.msdn.microsoft.com/vcblog/2016/12/12/december-update-for-the-visual-studio-code-cc-extension/#map to remap the paths.