Notices by Timo the timo (timotimo@peoplemaking.games)

@foone this doesn't exactly go in the right direction, but have you played with `rr` yet? the record&replay tool. runs on linux x86_64 and is capable of recording graphical programs as well. in fact, it's been developed for use with firefox.
it may not be trivial to trace back from screen pixel contents to map file contents, but being able to set a hardware watchpoint and then run execution backwards until you hit it is absolutely magical.
you use the replay part of rr with gdb, which you'd then probably want to script in python (or guile).
there's a paid offering from the rr developers called "pernosco" which has a "trace any value backwards through instructions" that also lets you do that for pixels on the graphical output of your program.
in any case, rr has been huge for bug hunting for me, maybe you can find a place for it in your heart^Wtoolbox as well

@whitequark have you already considered just a simple OBS screen capture with OBS's replay buffer feature?

otherwise `while true; do sleep 60; import -root screenshot_$(date)_.png; done` with something to expire old files (logrotate? lol) could do a lot

@foone holy shit i would have expected the system to absolutely crash if you just yank the GPU but i guess windows has that "your video driver crashed so we restarted it" feature nowadays? actually, i would have expected the gpu to take damage from that but maybe i don't give pci enough credit