clog-cli
CodeLLDB
| clog-cli | CodeLLDB | |
|---|---|---|
| - | 23 | |
| 864 | 2,618 | |
| 0.9% | - | |
| 7.1 | 8.7 | |
| 4 months ago | 28 days ago | |
| Rust | Rust | |
| 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.
clog-cli
We haven't tracked posts mentioning clog-cli yet.
Tracking mentions began in Dec 2020.
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?
rr - Record and Replay Framework
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
docker-rust - The official Docker images for Rust
nvim-dap - Debug Adapter Protocol client implementation for Neovim
cargo-deb - A cargo subcommand that generates Debian packages from information in Cargo.toml
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
emacs-racer - Racer support for Emacs
just - 🤖 Just a command runner
rst - The open source design documentation tool for everybody [Moved to: https://github.com/vitiral/artifact]
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
cargo-linked - Display linked packages for compiled rust binaries