mirror of
https://github.com/mihawk-99/PS5_RetroArch.git
synced 2026-10-22 00:22:29 -05:00
Mihawk
171ddc837e
Four console runs, each changing exactly one thing, with a marker in the entry point so the trace says which variant ran: -f -c cfg --verbose --menu config read SIGSEGV, rip=0 -f -c cfg --menu config read SIGSEGV, rip=0 -c cfg --menu config read SIGSEGV, rip=0 -f --verbose --menu no config runs, menu on screen So it is not --verbose taking effect for the first time, and not video_fullscreen either: dropping each leaves the crash. It is the config file being read at all. The config itself parses: marking config_load before and after prints both probes, so defaults, parse and config_load_file all return. The crash is after the read and before the first frame - no ps5_frame 0 line, and neither runloop_iterate call site in rarch_main is reached. It is inside retroarch_main_init, in the stretch between the config load and the first frame. drivers_init and video_driver_init_internal both complete (overlay, context reset, display server, mouse cursor, audio init, core info all mark), and ps5_input_init is never entered, so the input driver is not involved. What remains in that stretch is the driver lookups - audio, video, input, camera, menu - each indexing a driver table this build has stripped to almost nothing, and that is where the next marker goes. The title is back in its working state: entry argv complete, the config-path patch parked in parked/config-path.patch.py, input_driver left at "null" so the menu shows. gates: bash tools/verify.sh -> PASS. reproduce: bash tools/run-title.sh --watch 10.