clog-cli
rr
| clog-cli | rr | |
|---|---|---|
| - | 113 | |
| 864 | 9,224 | |
| 0.9% | 0.6% | |
| 7.1 | 9.6 | |
| 4 months ago | 10 days ago | |
| Rust | C++ | |
| MIT License | GNU General Public License v3.0 or later |
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.
rr
-
Don't Look Down on Print Debugging
https://learn.microsoft.com/en-us/windows-hardware/drivers/d...
Or on Linux use rr (https://rr-project.org/) or Undo (https://undo.io - disclaimer: I work on this).
These have the advantage that you only need to repro the bug once (just record it in a loop until the bug happens) then debug at your leisure. So even rare bugs are susceptible.
rr and Undo also both have modes for provoking concurrency bugs (Chaos Mode from rr - https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mo..., Thread Fuzzing from Undo - https://undo.io/resources/thread-fuzzing-wild/)
- Seer: A GUI front end to GDB for Linux
-
Net 9.0 LINQ Performance Improvements
> IntelliTrace is one that comes to mind - there’s nothing remotely close to it’s snapshot debugging that I’ve seen anywhere else, and I’ve really looked.
https://rr-project.org/
- Greppability is an underrated code metric
-
Tbsp – treesitter-based source processing language
Hi, in case you're not already aware of the name clash, there's already a `rr` in the programming world. It's "record and replay": https://rr-project.org/.
Very different, but a very fine tool tool.
-
Deterministic Replay of QEMU Emulation
I don't know, however a key element is:
> Record/replay system is based on saving and replaying non-deterministic events
> The following non-deterministic data from peripheral devices is saved into the log: mouse and keyboard input, network packets, audio controller input, serial port input, and hardware clocks (they are non-deterministic too, because their values are taken from the host machine). Inputs from simulated hardware, memory of VM, software interrupts, and execution of instructions are not saved into the log, because they are deterministic and can be replayed by simulating the behavior of virtual machine starting from initial state.
So, it's probably not much, you can probably comfortably save minutes of qemu sessions.
Also note the existence of the rr debugger [1], which allows you to reverse debug applications with a ~10% performance hit while recording. To achieve this, it records results of syscalls (only). It will serialize thread events, so have the effect of running applications like on a single core CPU.
[1] https://rr-project.org/
-
How does it feel to test a compiler?
rr.
rr rr rr rr.
rr!
When testing "algorithmic" modules like compilers, it's basically a productivity cheat code to run the tests under https://rr-project.org/. Doing so allows you to deterministically replay execution, seeking forwards and backwards in the timeline of your program's execution, and quickly locate what went wrong in any computation.
For example, if we have
struct CircleDescription { -
rr – record and replay debugger for C/C++
It says on https://rr-project.org/ that it supports Go programm, what's the status?
-
GTFL – A Graphical Terminal for Common Lisp
This was because no matter how hard I tried, I kept running into variables that I was watching that appeared to be the same reference, have different values (so I know I was referring to something wrong, but could not for the life of me figure it out, and though if I only had a way to step/trace and do this visually like an AST that highlights changed values and you could see back to its root where it's actually being modified visually)
I found out there's a thing called "deterministic debugging" (and the biggest known example afaict is rr: https://rr-project.org/
Apparently MS has a time-travel debugger... I pictured the AST being populated and repopulated via the steps, and the ability to diff changes over time.
Here's a wiki on various systems, though most of these seem to be typical text based "trace" options.
https://en.wikipedia.org/wiki/Time_travel_debugging
- rr: Lightweight Recording and Deterministic Debugging
What are some alternatives?
docker-rust - The official Docker images for Rust
CodeLLDB - A native debugger extension for VSCode based on LLDB
cargo-deb - A cargo subcommand that generates Debian packages from information in Cargo.toml
Module Linker - browse modules by clicking directly on "import" statements on GitHub
emacs-racer - Racer support for Emacs
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
rrweb - record and replay the web
nbdev - Create delightful software with Jupyter Notebooks
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
rustfmt - Format Rust code