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'm not sure precisely how the information/configuration from these sources should be combined, particularly given that the behaviour of rust-gdb is rather opaque (see #2532). Probably some experimenting would determine the right combination of things, and then we could have a rust-rr wrapper.
The text was updated successfully, but these errors were encountered:
The rust-gdb wrapper is provided from the https://github.com/rust-lang/rust project in the compiler component. Nominally the best way to get this resolved would be to get the wrapper into the compiler repo and exported into the channel components. From there we can add a proxy wrapper in rustup and then we're connected end-to-end. Short-term if you've managed to record with a plain rr record target/debug/blah then you might get away with env RUST_GDB="rr replay" rust-gdb
@rust-lang/compiler I'm not sure if you're quite the right team to ping, but what do we think about providing a rust-rr wrapper which then we could provide a rustup proxy for?
I would like to use
rr
(the time travelling debugger) with Rust.I found the following resources:
rust-gdb
wrapper, which seems from looking at strace to do some gdb configurationI'm not sure precisely how the information/configuration from these sources should be combined, particularly given that the behaviour of rust-gdb is rather opaque (see #2532). Probably some experimenting would determine the right combination of things, and then we could have a
rust-rr
wrapper.The text was updated successfully, but these errors were encountered: