mirror of
https://github.com/ARMSX2/ARMSX3.git
synced 2026-08-24 16:58:52 -07:00
jpolo1224
df1cb84789
The 1 KiB base+offset window measured nothing. On the hung device it reported tracked=1 longest=0s: one running thread, whose cia left the window every second, so the window reset on every tick and the counter never advanced past zero. The loop is wider than a handful of instructions -- it polls and calls helpers -- which the previous shape could not represent at all. Track the RANGE cia has covered instead, and allow 64 KiB of it. A polling loop that calls helpers stays within tens of KiB; ordinary execution covers megabytes in a second. The state line now reports the widest range being tracked. If this still does not fire, that number is itself the answer -- it says how large the loop really is, and therefore what the threshold must be, instead of costing another reproduction to find out.
