Body:
When executing the game program with Box64, a crash occurs consistently at the same x86 address, irrespective of the Dynarec setting (BOX64_DYNAREC=0 or =1). The crash results from a SIGILL (Illegal Instruction) signal, indicating that Box64 is unable to handle the x86 opcode 0F 3F. This opcode is non-standard and rarely seen in normal applications; it is suspected to be part of the game's copy protection or anti-tampering mechanism.
Crash Log:
0x595a2f: Dynarec stopped because of x86 Opcode 0F 3F 07 0B 64 8F 05 00 00 00 00 83 C4 04 83
SIGILL: Opcode at ip is 0f 3f 07 0b 64 8f
Environment:
· Box64: v0.4.5
· Architecture: ARM64 (Cortex-A510)
· OS: Android (Termux)
· Wine: 10.0-4proton-vanilla-wow64
BOX64_DYNAREC=0-trace-28042-1.txt
BOX64_DYNAREC=1-trace-28721-1.txt
Body:
When executing the game program with Box64, a crash occurs consistently at the same x86 address, irrespective of the Dynarec setting (BOX64_DYNAREC=0 or =1). The crash results from a SIGILL (Illegal Instruction) signal, indicating that Box64 is unable to handle the x86 opcode 0F 3F. This opcode is non-standard and rarely seen in normal applications; it is suspected to be part of the game's copy protection or anti-tampering mechanism.
Crash Log:
Environment:
· Box64: v0.4.5
· Architecture: ARM64 (Cortex-A510)
· OS: Android (Termux)
· Wine: 10.0-4proton-vanilla-wow64
BOX64_DYNAREC=0-trace-28042-1.txt
BOX64_DYNAREC=1-trace-28721-1.txt