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 Wow64EnableWow64FsRedirection function (called by XmlCreateDocument) is declared as returning BOOL (32 bit). However it actually returns BOOLEAN (8 bit).
This means the upper 24 bits may be filled with garbage, which can lead to interpreting a return value of FALSE as TRUE. The effect of this would be termination without any error message (via ::ExitProcess(1); in the same function).
Most of the time this error will not be noticeable in practice because due to the implementation details of this function the "garbage" is determined by the last error value. The most common error code is ERROR_CALL_NOT_IMPLEMENTED (on 32-bit versions of Windows) with a value of 120, so the upper 24 bits happen to be zero; a rarer error code above 255 would exhibit this problem however.
Originally opened by thfabba
The text was updated successfully, but these errors were encountered:
src/libs/dutil/xmlutil.cpp: pfnEnableWow64 = (BOOL (WINAPI *)(BOOLEAN))::GetProcAddress(hKernel32, "Wow64EnableWow64FsRedirection");
The Wow64EnableWow64FsRedirection function (called by XmlCreateDocument) is declared as returning BOOL (32 bit). However it actually returns BOOLEAN (8 bit).
This means the upper 24 bits may be filled with garbage, which can lead to interpreting a return value of FALSE as TRUE. The effect of this would be termination without any error message (via ::ExitProcess(1); in the same function).
Most of the time this error will not be noticeable in practice because due to the implementation details of this function the "garbage" is determined by the last error value. The most common error code is ERROR_CALL_NOT_IMPLEMENTED (on 32-bit versions of Windows) with a value of 120, so the upper 24 bits happen to be zero; a rarer error code above 255 would exhibit this problem however.
The text was updated successfully, but these errors were encountered: