https://bugs.winehq.org/show_bug.cgi?id=36094
--- Comment #2 from Austin English austinenglish@gmail.com --- I get a different but somewhat similar error: ../../../tools/runtest -q -P wine -T ../../.. -M advapi32.dll -p advapi32_test.exe.so security && touch security.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 ==15419== Syscall param writev(vector[...]) points to uninitialised byte(s) ==15419== at 0x4350DC7: writev (writev.c:26) ==15419== by 0x487B322: send_request (server.c:213) ==15419== by 0x487C094: server_call_unlocked (server.c:273) ==15419== by 0x48928D7: virtual_locked_server_call (virtual.c:3011) ==15419== by 0x4869E85: server_ioctl_file (file.c:4732) ==15419== by 0x486D515: NtDeviceIoControlFile (file.c:5563) ==15419== by 0x486D5EB: get_mountmgr_fs_info (file.c:1975) ==15419== by 0x487036A: NtQueryVolumeInformationFile (file.c:6382) ==15419== by 0x48601D1: __wine_syscall_dispatcher (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.so) ==15419== by 0x7BC33DBB: NtQueryVolumeInformationFile (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==15419== by 0x7B03A615: GetFileInformationByHandle (file.c:2930) ==15419== by 0x7B03BE56: CopyFileExW (file.c:528) ==15419== by 0x7B03C197: CopyFileW (file.c:591) ==15419== by 0x541B87E: do_file_copyW (queue.c:1127) ==15419== by 0x541BC1C: queue_copy_file (queue.c:1308) ==15419== by 0x541D984: SetupCommitFileQueueW (queue.c:1455) ==15419== by 0x5411750: SetupInstallFromInfSectionW (install.c:1101) ==15419== by 0x5411F3D: InstallHinfSectionW (install.c:1273) ==15419== by 0x41F325F: ??? (in /home/austin/wine-valgrind/programs/rundll32/rundll32.exe.so) ==15419== by 0x41F3C4B: wWinMain (rundll32.c:345) ==15419== Address 0x50aec28 is on thread 1's stack ==15419== in frame #7, created by NtQueryVolumeInformationFile (file.c:6184) ==15419== Uninitialised value was created by a stack allocation ==15419== at 0x486FE5A: NtQueryVolumeInformationFile (file.c:6184)
that code has been refactored recently, so I'm not sure if this is a different issue or just the new codepath.