Skip to content

Rustler: bound early ARM64EC startup diagnostics - #34

Open
butilly wants to merge 1 commit into
mainfrom
fix/rustler-fexcore-startup-diagnostic
Open

butilly wants to merge 1 commit into
mainfrom
fix/rustler-fexcore-startup-diagnostic

Conversation

@butilly

@butilly butilly commented Nov 15, 2026

Copy link
Copy Markdown
Owner

Game: Rustler - Grand Theft Horse (Epic), Rustler.exe and UnityCrashHandler64.exe. Thread: 1571482272253747222. Proton 9 ARM64EC with FEXCore 2603 and 2605 reproduces black startup. Latest report: 473 c000001d exceptions in UnityCrashHandler64.exe, first native frames libarm64ecfex.dll+0x171BFC, +0x17B31C, +0x17C520; guest frame UnityCrashHandler64.exe+0x5C5A0. Rustler loads UnityPlayer and later becomes idle. FEX stderr enabled: module logs in Rustler, no helper startup/assertion detail. Existing exception DFmt runs only with thread state and Logging::Init runs after LoadConfig, so repeating that capture cannot diagnose pre-logger failure. Diagnostic round 1 adds executable-scoped allocation-free bounded Wine stage output, temporary error/assert handlers after CRT through config loading, and native illegal-instruction PC plus FEX base before the thread-state guard. Normal logging and exception behavior remain unchanged. Preserve Proton 9 and ARM64EC; no game patch or graphics changes. Expected next evidence: FEX-STARTUP last completed stage and early assertion or native PC; compare helper and main-process progress independently. Diff check passed; compile/package validation through CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant