1/ Record-and-replay debugging has changed the way I work as a software engineer working on browser engines. I made a video showing how I used rr to debug one bug in Chromium. drive.google.com/file/d/15Ef… Some Chromium colleagues found this useful, so I'm sharing it here too.

Dec 22, 2021 · 9:03 PM UTC

4
21
2
88
2/ Some relevant links: rr-project.org/ is the open-source debugger I was using. bugs.chromium.org/p/chromium… is the bug I was debugging.
3
1
2
3/3 I hope to do a similar video sometime soon showing Pernosco pernos.co/ (a commercial product), which is even more powerful, and what I've been using for most of my debugging lately. My first attempt at a video didn't work out that well, though.
1
3
4
I did do the @_pernosco_ video, posted in this separate thread:
1/5 Last week I mentioned I'd also share a demo of @_pernosco_, which is a debugger whose interface is designed for record-and-replay debugging, although the debugging itself is less about replay than about moving between program states of interest.
Replying to @davidbaron
You definitely want to use `watch -l`, yes.
1
I'm aware... but at the same time I've come to expect things to have behavior subtly different from what I want. And the documentation wasn't very clear to me.
1
This tweet is unavailable
That sounds pretty different from what I was demonstrating (debugging browser bugs rather than web content bugs); @replayio is more relevant to that.
1
1