summaryrefslogtreecommitdiffstats
path: root/newlib/libc
diff options
context:
space:
mode:
authorCorinna Vinschen <corinna@vinschen.de>2016-03-09 23:10:17 +0100
committerCorinna Vinschen <corinna@vinschen.de>2016-03-09 23:10:17 +0100
commit48511f3d3847c35352d09cded56e25f0c1b22bc9 (patch)
tree1d87a108e94c24b6c8adf381fedfd6d7afc900b3 /newlib/libc
parent264b5e137e20d0a8062497f8555759eb8bf8cc02 (diff)
downloadcygnal-48511f3d3847c35352d09cded56e25f0c1b22bc9.tar.gz
cygnal-48511f3d3847c35352d09cded56e25f0c1b22bc9.tar.bz2
cygnal-48511f3d3847c35352d09cded56e25f0c1b22bc9.zip
Overwite potentially faked kernel version with correct values
* ntdll.h (RtlGetNtVersionNumbers): Declare. * wincap.cc (wincapc::init): Overwrite kernel version info returned by RtlGetVersion with correct info returnd by RtlGetNtVersionNumbers. Add comment. Originally, using RtlGetVersion instead of GetVersionEx was supposed to fix the fact that GetVersionInfo returns the wrong kernel version if the executable has been built with an old manifest (or none at all), starting with Windows 8.1. Either this never really worked as desired and our testing was flawed, or this has been changed again with Windows 10, so that RtlGetVersion does the kernel faking twist as well. Since we're only reading the value in the first process in a process tree. the entire process tree is running with a wrong OS version information in that case. Fortunately, the (undocumented) RtlGetNtVersionNumbers function is not affected by this nonsense, so we simply override the OS version info fields with the correct values now. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
Diffstat (limited to 'newlib/libc')
0 files changed, 0 insertions, 0 deletions