3 ms·

Only if you're debugging tests. Unfortunately using rr to debug a bigger application with lots of RAM access is not feasible.

• ObscureScience 4y ago
  Is that true? I genuinly have no experience with it. In their example they debug Firefox which I would consider a big application. Of course there are many levels above, and maybe you are talkning about tens of GB of memory usage?
  • thegeomaster 4y ago
    I haven't tried with FF personally, but the issue I have is that the traces are huge and reverse execution through memory-intensive codepaths takes a very long time, making the experience really slow. Or you can run a release build (with optimizations), in which case everything gets inlined, your asserts get nuked, and you're unable to inspect state well enough to figure out what's going on. In most cases, an ordinary debugger provides a better UX for me, but for the odd memory bug untraceable by normal hardware breakpoints in a traditional forward debugger, it comes in handy.
    • roca 3y ago
      Please file an rr issue and tell us more about your situation. Memory size and traffic shouldn't really be a problem. Multicore parallelism is the main problem. I've used rr with some very memory-hungry apps with good results.
• planede 4y ago
  That does not mirror my experience.