Skip to content

Windows: report inaccessible software interrupts as access violations - #23

Open
butilly wants to merge 1 commit into
mainfrom
fix/ddo-fexcore-interrupt-fix
Open

butilly wants to merge 1 commit into
mainfrom
fix/ddo-fexcore-interrupt-fix

Conversation

@butilly

@butilly butilly commented Nov 5, 2026

Copy link
Copy Markdown
Owner

Game: Dragons Dogma Online; process DDO.exe (WOW64), launched by DDO_Launcher.exe. Thread: 1567764075289640970. Latest report: FEX 2601-217d039-0 repeatedly logs Unknown interrupt: 0x1 immediately before c000001d, with median 0 FPS and a 72% main thread until quick-menu quit. Guest EIP 0x22cd22d is one captured site. The decoder emits SIGSEGV/#GP with an IDT selector for INT imm8, but the Windows frontend falls through to illegal instruction. Match Wine ntdll signal_i386.c/signal_x86_64.c: return access violation, two parameters (read, guest-width all-ones address), with faulting IP unchanged. Keep dedicated interrupt cases and ICEBP/single-step handling unchanged. This is architectural exception translation, not an instruction bypass or a game-file modification. Validation: diff --check passed; reference Wine ntdll invalid-interrupt tests expect these records for both guest widths. CI must compile both Windows frontends; on-device validation remains required. Expected result: replace the interrupt-derived c000001d records with c0000005 and determine whether game exception handling progresses past the black screen.

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