mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-16 13:59:56 -04:00
The review of the fatal summary change found that dispatch.c fatal_end called perf_summary_flush_try (ft_stop waits up to 50 ms, then the summary and the stutter map are formatted) before rtss_limit_restore and rt_rumble_stop_bounded. The lane's order for the failed ends, and A-6's for the orderly ones (gfx_present.c rt_exit_steps), puts what a kill of the process must not lose first: RTSS's profile and the controller's rumble. perf_summary_flush_try now runs after the restore and the bounded rumble stop, just before the stdio flushes and plat_terminate. The summary's lines still reach the log: rt_log_sync ran at the start of fatal_end, so every later line is written as it is made. Not reproduced before the change (an order of steps). tests/fatal_exit_check.py checks statically that fatal_end calls perf_summary_flush_try after rt_rumble_stop_bounded; the check fails on the code before this change and passes after it, and the program's cases (fatal, fatal_rumble, crash_crash, fatal_crash, crash_fatal) pass. The compile check of dispatch.c passes with no -Wall warnings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
14 KiB
14 KiB