- 94comments
- 9comments
- 1comments
- 466comments
- 115comments
- 199comments
- 18comments
- 150comments
- 50comments
- 62comments
- 214comments
- 4comments
- 80comments
- 3comments
- 74comments
- 17comments
- 47comments
- 8comments
- 18comments
- 34comments
- 28comments
- 44comments
- 90comments
- 342comments
- 33comments
- 31comments
- 1comments
- 4comments
- 38comments
- 378comments
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.