#RustRover debug
8 messages · Page 1 of 1 (latest)
fwiw manually running this works:
rust-lldb -o r -o bt -- /Users/<user>/Projects/learning/rust/lists/target/debug/deps/lists-54672fc1f3a44172
I have noticed 2 issues with RustRover debugging.
- Some variables are impossible to watch.
- Breakpoints added to lines of code that don't do anything by themselves will result in no break at all. For example, if I have a for loop, a breakpoint on the line that has the "for" keyword will be ignored. The workaround is either choosing a different line of code or adding a useless print statement and using that as the breakpoint.
But I never got the kind of problem that you are describing.
I'm not on Mac, so I haven't encountered the Mac specific bugs.
macos usually requires auth to debug a process, and rustrover probably doesn't ask for it properly and it just fails; I don't know how to help you tho