3 ms·
You should give RR or Pernosco a try. They both make it easy to record the program, stop execution at the crash, and then step backwards to see what went wrong.
by db48x 6y ago
You should give RR or Pernosco a try. They both make it easy to record the program, stop execution at the crash, and then step backwards to see what went wrong.
But honestly, even an ordinary debugger would let you print the value of the iteration variable at the point of the crash, along with all the other variables. I think your example was much too simplified.
- danaris 6y agoThose tools sound cool, but they appear to be specific to a few languages on Linux, none of which has ever significantly applied to me (I've been a Mac user my whole life). As for the other, that's sometimes true, and sometimes not; depends on what GUI debugger you're using. To be honest, it's been long enough since I was regularly working on languages with a non-terrible GUI debugger that I don't recall off the top of my head whether theirs did allowed that or not. These days, I'm mostly working in PHP, and unless something's changed quite recently, the only GUI debugging tools available for it require using Eclipse or similar godawful monstrosities. I will gladly eschew the benefits of such tools, and suffer the slings and arrows of snooty and judgmental developers like yourself (which I already get in plenty just for staining my hands with PHP), if it means that I don't have to use those lumbering behemoths every time I go to write or debug some code.
- db48x 6y ago> Those tools sound cool, but they appear to be specific to a few languages on Linux, none of which has ever significantly applied to me (I've been a Mac user my whole life). Correct. The author’s premise is that if we didn’t neglect our tools so much, all debuggers for all languages on all platforms could be that cool.