Skip to content

Just Cause 2: bounded WOW64 guest fault diagnostics - #32

Open
butilly wants to merge 1 commit into
mainfrom
fix/justcause2-box64-fault-diagnostic
Open

butilly wants to merge 1 commit into
mainfrom
fix/justcause2-box64-fault-diagnostic

Conversation

@butilly

@butilly butilly commented Nov 21, 2026

Copy link
Copy Markdown
Owner

Just Cause 2 (JustCause2.exe), thread 1573634430554079352: gameplay access violation reproduced on Box64 0.3.6 and 0.4.2 with BOX64_SHOWSEGV=1 BOX64_SHOWBT=1 BOX64_LOG=1. Latest report terminates at 250 seconds with wowbox64.dll+0x3BB0A0, nested exception frames and no guest address. No contemporaneous memory pressure or thermal throttling. Existing Linux signal diagnostics are not compiled into WOWBox64; the reset handler logs only its pointer at LOG_DEBUG. Add per-exe bounded logging of the original native exception, software signal origin, saved guest EIP/ESP and mapped JIT guest address plus allocation offset before reset/retry. Saved guest state is explicitly labeled as potentially stale. Keep exception policy unchanged and keep the member on Proton 11 arm64ec. This is diagnostic round 1, not a claimed crash fix. Reproduce the same area; inspect WOWBOX64-FAULT and WOWBOX64-EMIT alongside loader addresses to identify ownership and a patchable call site.

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