CodeLLDB
flowistry
| CodeLLDB | flowistry | |
|---|---|---|
| 23 | 15 | |
| 2,327 | 1,819 | |
| - | - | |
| 7.3 | 7.3 | |
| 2 months ago | 3 months 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.
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
flowistry
- An IDE plugin for Rust that helps you focus on relevant code
- Flowistry: an IDE plugin that analyzes the information flow of Rust programs, showing whether it's possible for one piece of code to affect another
-
Any data flow visualization tools?
https://github.com/willcrichton/flowistry https://github.com/cognitive-engineering-lab/aquascope
-
When do Rust's traits make your life difficult?
Hello Rustaceans, the same lab that has brought you The Rust Book Experiment, Aquascope, and Flowistry is starting a new endeavor. We want to understand when Rust's trait system makes it hard for you to understand or debug a Rust program.
-
rustc-plugin: A framework for writing plugins that integrate with the Rust compiler
I'm personally excited about building developer tools with a sophisticated understanding of your Rust programs. So I've worked on tools like Flowistry and Aquascope.
-
[blog] Rust should own its debugger experience
Maybe this vscode extension could be useful to you?
-
Plugins/extensions for the Rust Analyzer?..
Maybe you would be interested in flowistry?
- flowistry plugin?
-
Learn You an Agda (2014)
Quick, easy formal verification tools that programmers can use on the spot from the IDE are hard to make for most languages because most languages and their compilers weren't made with such thing in mind.
I guess Rust might be heading somewhere interesting with tooling, with tools like Flowistry existing (https://github.com/willcrichton/flowistry) showing what is possible. It's a plugin that can compute backwards / forwards static slices for you, straight in the IDE as a VSCode plugin. I think you need an external program that runs a full program analysis to do the same in C++.
-
Visual lifetime indicator
Based on how Flowistry works I think this should be possible.
What are some alternatives?
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
rustviz - Interactively Visualizing Ownership and Borrowing for Rust
nvim-dap - Debug Adapter Protocol client implementation for Neovim
code2flow - Pretty good call graphs for dynamic languages
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
just - 🤖 Just a command runner
wslgit - Use Git installed in Bash on Windows/Windows Subsystem for Linux (WSL) from Windows and Visual Studio Code (VSCode)
rst - The open source design documentation tool for everybody [Moved to: https://github.com/vitiral/artifact]
dbgee - The zero-configuration debuggee for debuggers. Handy utility that allows you to launch CLI debuggers and VSCode debuggers from the debuggee side.
cargo-linked - Display linked packages for compiled rust binaries
shisho - Lightweight static analyzer for several programming languages