Skip to content

WOW64: bounded DDO exception-context diagnostic - #24

Open
butilly wants to merge 2 commits into
mainfrom
fix/ddo-fexcore-exception-diagnostic
Open

butilly wants to merge 2 commits into
mainfrom
fix/ddo-fexcore-exception-diagnostic

Conversation

@butilly

@butilly butilly commented Nov 5, 2026

Copy link
Copy Markdown
Owner

Game: Dragons Dogma Online; exe DDO.exe; thread 1567764075289640970. Follow-up to PR 23, preserving its software-interrupt translation. Report 1567783618359726100 still shows a black screen and repeating guest EIPs 022cd22d/0245069c (host c0000005), 0227d3c5/0095a60b/03be6dd9/03df1681 (host c000001d translated to guest breakpoint/single-step). DDO itself ran about 46 seconds, not the 469-second launcher-inclusive session. Existing FEX pc/eip/code trace runs before translation and omits fault metadata, opcode bytes and memory protection; verbose SMC logging truncated 18 MB. Diagnostic only: DDO-scoped Wine output, first 32 exceptions then powers of two through 65536 (43 samples maximum); OS-mediated instruction reads, host and translated guest records, flags/debug registers and memory permissions. No exception semantics, Proton version or architecture changes. Validate that FEX-WOW64-DIAG records distinguish synthetic execute faults, INT imm8, INT3 and INT1/TF paths before selecting a second behavioral fix. First diagnostic build in this thread. Diff whitespace check passed; CI validates compilation.

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