#RustRover debug

8 messages · Page 1 of 1 (latest)

steel juniper
#

Debugging with RustRover hasn't worked for me since installing it.

After ~1min of "Instantiating tests...", I get:

  • console tab:

Test framework quit unexpectedly

  • LLDB tab:

E0329 09:25:33.233013 3759149056 TCPClient.cpp:122] ERROR connecting 3 No such process

Here's the run configuration:

steel juniper
#

fwiw manually running this works:

rust-lldb -o r -o bt -- /Users/<user>/Projects/learning/rust/lists/target/debug/deps/lists-54672fc1f3a44172
hazy terrace
#

I have noticed 2 issues with RustRover debugging.

  1. Some variables are impossible to watch.
  2. 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.

steel juniper
#

yeah for me it never even attaches

#

also I forgot to mention I'm on macOS

hazy terrace
#

I'm not on Mac, so I haven't encountered the Mac specific bugs.

wraith dagger
#

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