- 68comments
- 54comments
- 458comments
- 114comments
- 5comments
- 1comments
- 194comments
- 10comments
- 146comments
- 40comments
- 62comments
- 209comments
- 3comments
- 4comments
- 13comments
- 70comments
- 42comments
- 187comments
- 16comments
- 32comments
- 1comments
- 27comments
- 33comments
- 339comments
- 43comments
- 84comments
- 4comments
- 38comments
- 368comments
- —discuss
Awesome!
How does this compare to reversible debugging in GDB? I guess it addresses the increased overhead (some say 1000x) that UndoDB tries to fix.
This sounds excellent, I'm looking forward to the next opportunity to give it a spin. The process tree aspect is particularly cool.
The rr-dev mailing list has this comment[0] from roc:
I expect rr 4.0 will be either ARM support or gdb reverse execution, whichever one is done first.
[0] https://mail.mozilla.org/pipermail/rr-dev/2014-December/0002...
As I previously had no idea what Rr is, I googled it a bit.
So for others: It's a tool to record executable execution and play it back later for debugging purposes.
http://rr-project.org/ http://rr-project.org/rr.html
As someone that works in R I find this fact funny that a language uses the name Rr. I can't image the pain of using Google to find an answer. I thought search Google with R was bad enough. R is also now 3.1 so that actually might hurt even more.