vscode-cpptools
CodeLLDB
Our great sponsors
vscode-cpptools | CodeLLDB | |
---|---|---|
62 | 23 | |
5,342 | 2,327 | |
0.7% | - | |
9.3 | 7.3 | |
8 days ago | 2 months ago | |
TypeScript | Rust | |
GNU General Public License v3.0 or later | 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.
vscode-cpptools
-
🚀 Exciting New Feature Proposal for C++ Developers: "Add Similar Function" in IntelliSense! 🚀
🔗 Link to GitHub Issue: Add Similar Function - https://github.com/microsoft/vscode-cpptools/issues/11477
-
How to enable pretty printers?
According to this: https://github.com/microsoft/vscode-cpptools/issues/3423 it seems to be at least somewhat possible to reuse natvis files from Visual Studio, but I have not tested that. Never really had the need to look at any non-vector container in the debugger.
-
How to Debug C/C++ with Visual Studio Code (From a Microsoft Software Engineer)
Thank you for the feedback! Perf is always an ongoing issue for us but I can say that we’ve recently allocated one of our senior engineers to take on more perf related issues. Something that really helps us out is if you could file reproducible steps that lead to your performance issue. This allows us to address the issues more readily. Please file your issues here: https://github.com/microsoft/vscode-cpptools/issues
-
How to Setup VSCode for C/C++ Programming (From a Microsoft Software Engineer)
Yes, see this github issue for an example: Add Ada to supported languages for debugging · Issue #10475 · microsoft/vscode-cpptools (github.com)
-
Me after trying to use Git with Eclipse
Nope https://github.com/microsoft/vscode-cpptools/issues/16
- [Vscodium] L'extension C / C ++?
- εχει τρεξει κανεις cuda σε visual studio code ;
-
I can't properly use "Run C/C++ file"
and finally, it you're not happy using the extension I provided you, try fo contact the C/C++ Extension repo on GitHub, they'll help you out with your issue. Here's the link: https://github.com/microsoft/vscode-cpptools
-
[Vscode] VSCode me donnant une erreur lorsque j’utilise le débogueur : "launch: program enter name n’existe pas"
Vous devez définir le nom de votre exécutable dans launch.json. Ils expliquent ce qu'il faut faire et comment ici : https://github.com/Microsoft/vscode-cpptools/blob/master/launch.md
- Need help debugging c++
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
What are some alternatives?
vscode-clangd - Visual Studio Code extension for clangd
nvim-dap - Debug Adapter Protocol client implementation for Neovim
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
just - 🤖 Just a command runner
rst - The open source design documentation tool for everybody [Moved to: https://github.com/vitiral/artifact]
Bear - Bear is a tool that generates a compilation database for clang tooling.
cargo-linked - Display linked packages for compiled rust binaries
vscode-clang-format - A Visual Studio Code extension that provides C++, C, Obj-C, Java formatting with the use of clang-format
Rustup - The Rust toolchain installer