vardump 11 years ago 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 baldfat 11 years ago 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.
baldfat 11 years ago 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.
robin_reala 11 years ago 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...
gaalze 11 years ago How does this compare to reversible debugging in GDB? I guess it addresses the increased overhead (some say 1000x) that UndoDB tries to fix.
lttlrck 11 years ago This sounds excellent, I'm looking forward to the next opportunity to give it a spin. The process tree aspect is particularly cool.
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.
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...
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.
Awesome!