Re:rr: lightweight recording and deterministic debugging
by roca on Tuesday November 06, 2018 @09:34AM
(#18391298)
FWIW Mozilla funded it until 2016 but since then Kyle Huey and I have been maintaining it out of our own pockets while we work on our startup.
Re:rr: lightweight recording and deterministic debugging
by Elv13 on Tuesday November 06, 2018 @09:50AM
(#18391439)
And thanks for keeping working on it ;)
After having this problem in GNU "high priority" list for a decade, it's nice to see this thing exist. My comment was more about the initial "make it happen" part. To me, `rr` seems like a really non trivial project to get going in the first place. Not a lot of orgs would have taken a risk with this.
Re:rr: lightweight recording and deterministic debugging
by roca on Tuesday November 06, 2018 @10:16AM
(#18391714)
We deliberately chose a design that could be implemented with a very small team. In fact there has never been more than about one person working full time on rr, usually less. That's one reason we bet on not using code instrumentation, for example.
But yes, Mozilla deserves major credit for supporting us building this crazy thing --- and of course, releasing it.
Re:rr: lightweight recording and deterministic debugging
by dman on Tuesday November 06, 2018 @09:35AM
(#18391307)
Have you publicly announced what the startup works on?
Re:rr: lightweight recording and deterministic debugging
by roca on Tuesday November 06, 2018 @09:40AM
(#18391349)
We haven't said much. https://robert.ocallahan.org/2018/05/update-pernosco.html
Re:rr: lightweight recording and deterministic debugging
by dman on Tuesday November 06, 2018 @09:56AM
(#18391499)
How do I pay for this?
Re:rr: lightweight recording and deterministic debugging
by roca on Tuesday November 06, 2018 @10:03AM
(#18391572)
Email me: [email protected]
In RR, you just have to reproduce the problem, then put a breakpoint back in time to when the state was good then reverse continue back there. It creates a very narrow window of debugging instead of hours of head scratching.
I wrote many GDB frontend extension for my personal use (they may or may not work for others and may by broken in python3, I am not a python dev). This one is very useful with RR. It allows to log "print" on auto-generated breakpoints then print them into a spreadsheet. https://gist.github.com/Elv13/92b98579e62f086cd9c12f44e510ca...
It's very useful with RR because you can modify the columns `print` as many time as you like and ask rr to regenerate it without executing again.