by levzettelin on 7/21/24, 8:54 AM with 131 comments
by whatsakandr on 7/21/24, 1:46 PM
by suby on 7/21/24, 11:08 AM
by laserbeam on 7/21/24, 12:12 PM
My limited understanding says a debugger needs: a list of symbols (.pdb files on windows, can't remember what they are on linux), understanding of syscalls and a few other similar things. I thought they don't care too much what generated the binaries they are debugging (obviously as long as it's native code).
Doesn't rr work with other languages like rust, zig, odin, nim, and similar ones? Obviously, I wouldn't expect it to work for python, js, c# and other languages with managed memory.
by rtpg on 7/21/24, 10:43 AM
Despite that, it would be very, very, very cool if some languages built rr directly into their tooling. Obviously you can always "just" use rr/gdb, but imagine if rr invocations were as easy to set up and do as pdb is in Python!
by modeless on 7/21/24, 4:11 PM
> [...] just click on the incorrect value. With full program history Pernosco can immediately explain where this value came from. The value is tracked backwards through events such as memcpys or moves in and out of registers until we reach a point where the value "originated" from, and each step in this process is displayed in the "Dataflow" panel that opens automatically. There is no need to read or understand the code and think about what might have happened, we can simply ask the debugger what did happen.
by ho_schi on 7/21/24, 8:43 PM
I assume rr provides more features and flexibility. Anyway I want to mention that GDB itself can already reverse debug for some time now.
by forrestthewoods on 7/21/24, 3:37 PM
https://www.forrestthewoods.com/blog/windbg-time-travelling-...
by dmitrygr on 7/21/24, 8:20 PM
by leoc on 7/21/24, 4:51 PM
by jfk13 on 7/21/24, 11:31 AM
https://news.ycombinator.com/item?id=31617600 (June 2022)
by teaearlgraycold on 7/21/24, 10:48 PM
Super useful, especially considering I know barely anything about x86-64.
by MaskRay on 7/22/24, 6:47 AM
rr record /tmp/Debug/bin/llvm-mc a.s && rr replay -d cgdb
I've have success story with some bugs only reproducible with LTO. Without rr it would be a significant challenge.
It would be nice if Linux kernel could be debugged with rr. Does anyone have success with kernel under rr+qemu ? :)
by alfiedotwtf on 7/22/24, 6:19 AM
by iamcreasy on 7/21/24, 11:27 PM
by boguscoder on 7/21/24, 3:08 PM
by whatsakandr on 7/21/24, 1:52 PM
by throwaway2037 on 7/22/24, 2:57 AM