Crash with illegal instruction under Windows 11 x64 ARM virtualization about libzip HOT 2 CLOSED

The line len = ZIP_LENGTH_TO_END just assigns 0 to an integer variable.
libzip is written in C, so it doesn't throw or catch exceptions.
I'm sorry, you'll have to debug this a bit more yourself. Perhaps start with adding error checking (the code you pasted has none, I hope your real code has much more).

from libzip.

The line len = ZIP_LENGTH_TO_END just assigns 0 to an integer variable. libzip is written in C, so it doesn't throw or catch exceptions. I'm sorry, you'll have to debug this a bit more yourself. Perhaps start with adding error checking (the code you pasted has none, I hope your real code has much more).

I know that it's just assigning 0 to a variable but it will be compiled as LDS EDI,ECX (I've personally checked this under debugger)
However, I can't seem to find the exact cause of why it can't run past that as it works fine under real x86-64 CPU.
I will come back here later after doing more investigation into this.

Edited:
It appears that for some reason, the AVX instruction set was the cause of this crash.
Particularly the option in Visual Studio Configuration Properties > C/C++ > Code Generation > Enable Enhanced Instruction Set. Apparently, those instruction set weren't supported or properly virtualized on the machine I ran the code.

I used a newer debugger (x64dbg) to view the code that caused the crash. Ollydbg's disassembler is outdated and does not support disassembling of AVX instructions that's why it was showing a completly different instruction.

from libzip.