-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rust-gdb doesn't set up path substitutions? #62945
Comments
Visited during wg-debugging's triage meeting. We think this is most likely still an issue but probably not a high priority one. If someone wants to work on this, the first thing they should do is retest and verify this is still broken (but we think it most likely is). There may be a fairly simple resolution to modify rust-gdb to detect which toolchain it's being invoked from and then run the set substitute-path path with the appropriate paths. I'm willing to help mentor someone in fixing this 🙂 |
Hi, I'm looking for a first issue, would love the mentoring! |
can't reproduce it, it works just fine nearly 4 yrs later, has this perhaps already been fixed @wesleywiser, @lnicola @Centril ? |
Past @lnicola should have included a sample test case. |
No, I can still reproduce it. @diogofriggo are you maybe using a distro-packaged toolchain? Crashing program: use std::sync::Once;
static INIT: Once = Once::new();
fn main() {
INIT.call_once(|| unsafe {
*(0xaabbccdd as *mut usize) = 1234;
});
}
To make |
…r=cuviper Set up standard library path substitution in rust-gdb and gdbgui Fixes rust-lang#62945 --- Only lightly tested (in release mode, where the paths are a bit of a mess) because my `gdb` appears to crash with `internal-error: inside_main_func: Assertion 'block != nullptr' failed.` and I don't have `gdbgui`. Please review carefully my shell syntax. There's also `rust-lldb`, but I don't know the equivalent for it.
I'm trying to use
rust-gdb
on project generated bycargo new
and looks like therust-src
source code path is not configured:The text was updated successfully, but these errors were encountered: