CodeLLDB
rust-tools.nvim
CodeLLDB | rust-tools.nvim | |
---|---|---|
23 | 90 | |
2,327 | 2,165 | |
- | - | |
7.3 | 0.0 | |
2 months ago | 4 months ago | |
Rust | Lua | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CodeLLDB
-
custom pretty printer/debug helpers for C++ debugging?
Ok, so apparently here they are called 'data formatters' instead of pretty printers or debug helpers... https://github.com/vadimcn/codelldb/wiki/Custom-Data-Formatters
-
Visualization tools when working with C++?
For debugging lldb supports python scripts: https://github.com/vadimcn/codelldb/wiki/Data-visualization
-
Zig Build System
I use VS Code on Linux to debug Zig. Haven't tried the others you mentioned, but it just emits standard DWARF symbols, so I'm guessing if you can debug C/C++ you could probably also do Zig with minimal changes? I just use the lldb VS code plugin[0], which works out of the box for me with no issues.
https://github.com/vadimcn/codelldb
-
How game-dev-s debug rust?
It's pretty bad, unfortunately. As you discovered, using the gnu toolchain works better with code-lldb (see more info here), but it still isn't great. CLion is a little better, but costs money and lacks support in other ways compared to VSCode.
- Debug rust program as root
-
Migrating from VSCode to Neovim
- I tried to install codelldb: https://github.com/vadimcn/vscode-lldb without success.
-
Does anyone here work in gamedev with Rust as their primary language?
Are you on Windows or Linux? On Windows I've had nothing but trouble getting code-lldb to display debug info for any sort of nontrivial data structure due to this issue, which means I need to switch to x86_64-pc-windows-gnu, but then that breaks other upstream crates that use cc to compile C++ code.
-
[blog] Rust should own its debugger experience
I've been using vscode-lldb with VS Code on macos, and I've been very happy with the experience so far.
-
i need some recommendations
Check this: https://github.com/vadimcn/vscode-lldb/wiki/Breakpoints-are-not-getting-hit
-
using VScode codeLLDB
yeah since they updated the rust compiler for windows to use a different style of debugger symbols and since they changed that in CodeLLDB the variables output have not been the same. Though i believe the owner has been trying to fix it. But any issues you do have report them on the codeLLDB git https://github.com/vadimcn/vscode-lldb
rust-tools.nvim
-
[Experimental] Auto find Rust executables for DAP | Linux
This is not a robust solution to the problem. I haven't worked on a large Rust project, so I do not know if this is valid for all kinds of Rust projects. Maybe there is a better debugging config setups/plugins out there (simrat39/rust-tools.nvim is one from what I have searched for). I plan to keep using this config, till it breaks; and try and fix it when it does.
-
NeoVim IDE setup
rust-tools is what I'm currently using, https://github.com/simrat39/rust-tools.nvim
-
What editor are you using for Rust?
I then took the snippet from, I also changed the path to the correct install path of the above. https://github.com/simrat39/rust-tools.nvim/wiki/Debugging
-
Neovim & Rust
rust-tools.nvim and crates.nvim should be helpful for you. :)
-
What's your current Vim+Rust setup?
I'd start with nvim-treesitter, nvim-lspconfig, and use rust-tools.nvim as an accelerant. Any remaining advice I'd have is about Neovim but not about Rust. That advice would also be mostly questions of taste for this-or-that decisions.
-
Refactoring
Are you using https://github.com/simrat39/rust-tools.nvim/ ?
-
Rust + Neovim setup gotcha
TIL that if you install Rust via Homebrew (like brew install rust), auto formatting (or more specifically, lsp formatting) doesn't work properly. I used both Rust Analyzer and rust-tools) to setup rust lsp and configured it with tons of options, thinking maybe something will work but somehow, one thing never did - auto formatting. This is the command I use for setting up auto formatting via lsp:
-
What setup do you use to program in rust?
neovim + native lsp with rust-tools.nvim, running nixos so I use flakes for my dev environments
- [Neovim] Rust-tools.nvim: outils pour des fonctionnalités supplémentaires sur Rust Analyzer
-
NVim, Rust, LSP (rust-analyzer + rust-tools) issue
I opened an issue https://github.com/simrat39/rust-tools.nvim/issues/369 after searching for such behavior in existing ones. But I also ask here in case it's a known problem.
What are some alternatives?
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
nvim-dap - Debug Adapter Protocol client implementation for Neovim
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
helix - A post-modern modal text editor.
just - 🤖 Just a command runner
nvim-cmp - A completion plugin for neovim coded in Lua.
rst - The open source design documentation tool for everybody [Moved to: https://github.com/vitiral/artifact]
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
cargo-linked - Display linked packages for compiled rust binaries
lsp_extensions.nvim - Repo to hold a bunch of info & extension callbacks for built-in LSP. Use at your own risk :wink: