CRusTTY: A pedagogical C interpreter with time-travel debugging capabilities
varun_ch
16 points
2 comments
March 11, 2026
Related Discussions
Found 5 related stories in 92.1ms across 8,303 title embeddings via pgvector HNSW
- Retrofitting JIT Compilers into C Interpreters ltratt · 65 pts · April 15, 2026 · 54% similar
- A tail-call interpreter in (nightly) Rust g0xA52A2A · 147 pts · April 05, 2026 · 48% similar
- The TTY Demystified (2008) 20after4 · 63 pts · May 19, 2026 · 47% similar
- A 6502 disassembler with a TUI: A modern take on Regenerator wslh · 14 pts · March 20, 2026 · 47% similar
- How to make a fast dynamic language interpreter pizlonator · 117 pts · April 21, 2026 · 46% similar
Discussion Highlights (2 comments)
anematode
Time travel debugging is soooo cool and I wish it was more widespread (of course I'm aware it's very difficult to implement and has unavoidable overhead). Imagine if an automated error report from a user of your app included not only a stack trace (or whatever have you), but the execution steps leading up to the error.
yjftsjthsd-h
This is NOT a production C interpreter: Subset of C (no preprocessor, typedefs, unions, enums, function pointers) No optimization or JIT compilation Limited standard library (only built-in functions) No file I/O or external system interaction Fixed memory sizes Still probably a good learning tool, but that does limit it to toy/teaching codebases, not real existing programs.