VsCode: generate configuration for debugging #3441
Comments
|
Isn't this the domain of vscode-lldb extension? |
|
nope, to run a test you need to know what a test is, and, with macros, only
rust-analyzer can really know that.
…On Thu, 5 Mar 2020 at 10:10, Veetaha ***@***.***> wrote:
Isn't this the domain of vscode-lldb
<https://github.com/vadimcn/vscode-lldb> extension?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3441>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANB3M7N7YLO3ACJE6RQ5S3RF5T65ANCNFSM4LBEJDFA>
.
|
|
#4366 already has the code to generate launch configurations, so I'll start work on this issue. |
matklad
pushed a commit
to matklad/vscode-rust
that referenced
this issue
Jul 13, 2020
4448: Generate configuration for launch.json r=vsrs a=vsrs This PR adds two new commands: `"rust-analyzer.debug"` and `"rust-analyzer.newDebugConfig"`. The former is a supplement to the existing `"rust-analyzer.run"` command and works the same way: asks for a runnable and starts new debug session. The latter allows adding a new configuration to **launch.json** (or to update an existing one). If the new option `"rust-analyzer.debug.useLaunchJson"` is set to true then `"rust-analyzer.debug"` and Debug Lens will first look for existing debug configuration in **launch.json**. That is, it has become possible to specify startup arguments, env variables, etc. `"rust-analyzer.debug.useLaunchJson"` is false by default, but it might be worth making true the default value. Personally I prefer true, but I'm not sure if it is good for all value. ---- I think that this PR also solves rust-lang/rust-analyzer#3441. Both methods to update launch.json mentioned in the issue do not work: 1. Menu. It is only possible to add a launch.json configuration template via a debug adapter. And anyway it's only a template and it is impossible to specify arguments from an extension. 2. DebugConfigurationProvider. The exact opposite situation: it is possible to specify all debug session settings, but it is impossible to export these settings to launch.json. Separate `"rust-analyzer.newDebugConfig"` command looks better for me. ---- Fixes #4450 Fixes #3441 Co-authored-by: vsrs <vit@conrlab.com> Co-authored-by: vsrs <62505555+vsrs@users.noreply.github.com>
RalfJung
pushed a commit
to RalfJung/rust-analyzer
that referenced
this issue
Apr 27, 2024
shims/unix: split general FD management from FS access `fd.rs` was a mix of general file descriptor infrastructure and file system access. Split those things up properly. Also add a `socket.rs` file where support for sockets can go eventually. For now it just contains the socketpair stub.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a feature request. VS Code has built-in support for debugging through CodeLLDB and VS Code cpptools. These extensions can generate configuration for launch.json through a menu that looks like this:
Getting the configuration right for Rust projects is a bit of a tricky one, with some nuance on how to properly target binaries, libraries, and tests across all major platforms. Since
rust-analyzeris providing a premier Rust experience in VS Code, this might be an interesting feature to add.References
The text was updated successfully, but these errors were encountered: