https://bugs.winehq.org/show_bug.cgi?id=52396
florian.will@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |florian.will@gmail.com
--- Comment #5 from florian.will@gmail.com --- I'm using the "dotnet dev-certs https" command to try and debug this, as it triggers the error and seems to be less multi-threaded/complex/long-running than other things I've attempted, and so I don't need to compile any dotnet executable myself.
According to "WINEDEBUG=+seh ./wine64 dotnet dev-certs https", it raises lots of code=0x02345678 exceptions, and then eventually ACCESS_VIOLATION exceptions, before the stack overflow happens. Apparently those 0x02345678 exceptions can be raised by the dotnet JIT compiler when it encounters invalid MSIL code ("InvalidProgramException"). Maybe this is also triggered on 64/32 bit mismatch when the dotnet runtime attempts to load native code from some DLL file, expecting it to be 32 bit but it turns out to be 64 bit, or vice versa? I honestly have no idea how that works. Or maybe something in wine makes the 64bit JIT compiler in dotnet6 believe that there is invalid MSIL code in managed executables files quite frequently.