I often sprinkle print statements around, but would also like to point out https://rr-project.org https://rr-project.org, which takes gdb-level debugging to a w

I often sprinkle print statements around, but would also like to point out https://rr-project.org https://rr-project.org, which takes gdb-level debugging to a whole new level. E.g. you hit an assertion in your code because some value was outside the expected range? Fine, set a watchpoint on it when the assertion fires, and simply reverse-continue to see where that value came from. It could change your debugging life...!