You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following code, if compiled as an x86_64 process and run on an arm64 system, will claim that the command shell binary is not executable. This is because GetBinaryTypeW returns ERROR_BAD_EXE_FORMAT for wow64 processes.
This is not necessarily a bug in Foundation, but a quirk in the Win32 APIs. It seems worth documenting this caveat, at least.
Thanks for catching this, I wonder if there's an alternative API that we can be using here that would allow us to determine if the file is executable even if the architectures don't match (or perhaps if we call GetBinaryTypeW and the error is ERROR_BAD_EXE_FORMAT, does that indicate that it is executable and we should add a special case to return true in that scenario?
The following code, if compiled as an x86_64 process and run on an arm64 system, will claim that the command shell binary is not executable. This is because GetBinaryTypeW returns ERROR_BAD_EXE_FORMAT for wow64 processes.
This is not necessarily a bug in Foundation, but a quirk in the Win32 APIs. It seems worth documenting this caveat, at least.
The text was updated successfully, but these errors were encountered: