My change was trivial, only affects a code path dealing with Mach-O files, and could not have caused these failures.
On Mar 6, 2019, at 7:22 PM, Marvin testbot@winehq.org wrote:
VM Status Failures Command debian9 failed 2 debian9 failed 2
You can also see the results at: https://testbot.winehq.org/JobDetails.pl?Key=48888
=== debian9 (32 bit report) ===
kernel32: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x7eb6885d).
Report errors: kernel32:virtual prints too much data (90431 bytes)
=== debian9 (32 bit Chinese:China report) ===
kernel32: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x7e9b385d).
Report errors: kernel32:virtual prints too much data (90431 bytes)
=== debian9 (32 bit WoW report) ===
kernel32: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x7eb6885d).
Report errors: kernel32:virtual prints too much data (90502 bytes)
=== debian9 (64 bit WoW report) ===
kernel32: Unhandled exception: page fault on write access to 0x00000000 in 64-bit code (0x00007f8786bbe8a1).
Report errors: kernel32:virtual prints too much data (87157 bytes) <debian9_win32.report><debian9_win32_zh_CN.report><debian9_log.txt><debian9_wow32.report><debian9_wow64.report><debian9_log.txt>