SIsidkshatriya·May 31, 2025Submission
Record/Replay Debugging Tutorial
14 points · Open discussionsidkshatriya
me
OPEN SOURCE2020–2025
sidkshatriya / me
me
This is a space where I express my thoughts and opinions on mostly technical things
4Distinct people
15Mentions
0Explicit recommenders
165GitHub stars
What to know before exploring
What it is
This is a space where I express my thoughts and opinions on mostly technical things
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year15 dated mentions
Observed mentions: 2020-08-12 10:38:44 UTC to 2025-05-31 13:24:17 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 5 | 4 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 6 | 5 | 1 |
What Hacker News says
15 sourcesRecord/Replay Debugging Tutorial
3 points · Open discussionDealing with GitHub Jealously (2021)
1 points · Open discussionBringing Record and Replay debugging everywhere on Linux
209 points · Open discussionBringing and Record and Replay everywhere
1 points · Open discussion_Software Counters mode_ `rr` is a reverse debugger built upon the awesome `rr` debugger.
It relaxes one major limitation with the `rr` debugger - it does NOT require access to CPU HW performance counters.
This allows the debugger to run in containers, cloud VMs etc where access to CPU performance counters is usually disabled or not available.
In case you're wondering: reverse debugging is a powerful approach to locating bugs in your program using record/replay. Please see the blog post (https://github.com/sidkshatriya/me/blob/master/008-rr-everyw...) for a gentle exposition of the concept behind record/replay.
In Bringing and Record and Replay everywhereMy Thoughts on OCaml vs. Haskell/Rust in 2023
21 points · Open discussionFrom one of the linked pages:
"Lack of garbage collection was a problem but runtimes are more troublesome...Linux signal handling becomes very complicated...Runtimes also often force layout of data structures be tuned to the needs of the garbage collector..."
https://github.com/sidkshatriya/me/blob/master/002-why-rust....
That sums up my experience using a lot of higher-level languages. The pitch is always that language X should replace C because it's just as fast in most practical cases but much easier and safer. But the reason I use C is because of the pain of complex runtimes, especially when interoperating with other languages.
And that's also why I'm interested in Rust. It's the first high-level language (I use the term loosely) that doesn't interfere with anything you're trying to do. It can even do dynamic dispatch on ordinary poin
Read the rest
ters to structures with a C memory layout, because it doesn't add a vtable pointer to structs (like C++ does).
"I don't know much about dlang -- it could have been the best of both worlds"
Yeah, I skipped over dlang, too. And I don't have a good reason for that, aside from a lack of time to really explore both. I hope dlang keeps growing and eventually I'll look into what it has to offer.
55,000 lines of Rust code later: A debugger is born
86 points · Open discussionWhy debuggers matter and rd, a debugger written in Rust
6 points · Open discussion45,000 lines of Rust code later: An update on the Record and Debug Tool (rd)
1 points · Open discussion45,000+ lines of Rust code later: An update on the Record and Debug Tool (rd)
5 points · Open discussionmozilla/rr [1] is an excellent and powerful record/replay debugger written in C/C++.
Over the last few months I've been working on porting rr to the Rust programming language. The port is still in-progress but many things work already.
Why is it is a good idea to port rr to Rust ? I've written a blog post about this at [2].
The project is called "The Record and Debug tool" or "rd" for short. The repo is available on GitHub [3].
Please give me your feedback and comments! Contributions to `rd` are welcome!
[1] https://github.com/mozilla/rr
[2] https://github.com/sidkshatriya/me/blob/master/001-rd-intro....
[3] https://github.com/sidkshatriya/rd
In Rd: A port of mozilla/rr to the Rust programming languageRd: A port of mozilla/rr to the Rust programming language
2 points · Open discussion