Add floor_watch: hardware watchpoints on the floor the scan finds log which game code reads and writes it, at 60 fps and again at 120 fps or more.

floor_watch.c takes up to twelve of the floor scan's survivors (the platform's rigid body controller unit first, then one per object at the pivot's height), watches them four at a time through the debug registers on every thread (platform.h plat_watch_set, Windows only), counts each access's call chain in a lock-free table and logs the chains with the executable's symbol names after each pass. prof_syms gains a callback form for that.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-13 07:08:09 -05:00
parent c84724da2c
commit cae09a2bcd
11 changed files with 492 additions and 8 deletions

View File

@@ -971,6 +971,10 @@
# then on. The snapshot holds the game for about a second once. 1 writes 20000 lines, a larger number that many; 0 is
# off.
# floor_scan = 0
# Diagnosis (Windows): 1 also runs floor_scan and, once it has found the floor, logs which code of the game reads and
# writes it: hardware watchpoints on its addresses for a few seconds at 60 fps, and again at the next stretch at 120
# fps or more with Link on the floor. Each pass slows the game for its few seconds. 0 is off.
# floor_watch = 0
# 1: with trace = perf, walks of the process's address space count its private and write-combined memory every 600
# frames (the "mem: process" line) and where its committed memory lies every 3600 frames (the "commit census" lines).
# Each walk holds the address-space lock for 100-240 ms and delays the next frame by as much, so they are off unless