Skip to content

FEX ARM64EC: diagnose Peeping Dorm Manager startup failure - #21

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

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

Conversation

@butilly

@butilly butilly commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Game: Peeping Dorm Manager; executable: Peeping Dorm Manager.exe. Thread: 1566679842768814182.
Evidence: FEXCore 2605 on Proton 11 ARM64EC exits with c000001d at libarm64ecfex+0x171BFC; caller chain includes +0x17B31C, +0x17C520, +0x17C3EC, +0x17F8DC, +0x102848 and game+0x1260. No Unity or graphics modules load. FEX_SILENTLOG=0 and FEX_OUTPUTLOG=stderr reproduce without game-process FEX messages.
Existing Logging::Init runs after InitSyscalls, CRT, thread handlers, executable naming and config loading. No existing early stage trace was found. Add allocation-free, bounded Wine startup stage messages with the Wine thread id, and temporary LogMan handlers after CRT until normal logging initialization. Preserve the trap and exception paths, configuration and Proton major/architecture. No speculative emulation workaround.
Validation: git diff --check; source review against LogMan handler signatures and Wine TEB; Windows compilation through package CI. Next run: inspect last completed ProcessInit stage and any early assertion/error, then correlate the crash thread. Diagnostic round 1; cause not yet established.

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