Sorry, since my first installing of rust, I have been always struggling with the debugger, neither gdb or lldb, works even in one of my Windows7, Fedora or openSUSE VS code.
I followed some instructions, step by step, nothing seems missing, but it just doesn't work, now I get the error after I start debugging after I installed the LLVM-5.0.0-r306282-win32.exe & python-3.5.3.exe, and VS code plugin LLDB debugger, then the VS code tells the LLDB self-test failed, and detailed message shows as below:
"(lldb) script import sys, io, lldb; print(lldb.SBDebugger.Create().GetVersionString()); print("OK") error: your copy of LLDB does not support scripting. --- An exception was raised while launching debugger: { Error: The debugger exited without completing startup handshake.
** at ChildProcess.lldb.on (C:\Users\abc.vscode\extensions\vadimcn.vscode-lldb-0.5.4\out\startup.js:166:27)**
** at emitTwo (events.js:106:13)**
** at ChildProcess.emit (events.js:191:7)**
** at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)**
** code: 'Handshake',**
** stdout: '(lldb) script import sys, io, lldb; print(lldb.SBDebugger.Create().GetVersionString()); print("OK")\r\n' }** "
I am downloading the exe provided by you, but the download speed seems very slow, and was always interrupted, I am still trying to get this exe, when it was done, I will let you know.
I tried the command line, the command "list", "breakpoint set --line 4" seems nothing wrong, but when I "run", it reported the same message: "error: process launch failed: 'A' packet returned an error: -1"
Don't know about lldb or gdb, but on Windows at least the Visual Studio debugger, which now is available with VSCode, works just fine. You just have to set up the right task/launch config.
I tried a little debugging with a single function in a single file in the Visual Studio, with the VisualRust plugin installed, it seems the debugging is close to OK, though may have some unexpected and unwanted loop by the debugger, at least it's OK to add a variable to watch. But the intelligence prompt and more other editing feature of VisualRust is not that satisfying, I will not like to use it.
I wasn't talking about debugging in Visual Studio, but rather debugging in VS Code. VS Code behind the scenes uses the C++ debugger available in Visual Studio. VS Code people call it the "Windows debugger" (I think). You won't need Visual Rust for this and the experience is quite good.
I don't know about Windows, but on Linux the IDE and visual Rust-debugger of CLion-2017.2 with Rust-Plugin works really well, just I had to purchase a license for CLion. One has got the chance to test using a 30 day license