1 files changed, 71 insertions, 0 deletions
diff --git a/results/classifier/118/none/1528718 b/results/classifier/118/none/1528718
new file mode 100644
index 000000000..223798107
--- /dev/null
+++ b/results/classifier/118/none/1528718
@@ -0,0 +1,71 @@
+semantic: 0.342
+x86: 0.231
+device: 0.216
+graphic: 0.205
+PID: 0.179
+files: 0.159
+architecture: 0.152
+socket: 0.141
+ppc: 0.124
+register: 0.119
+i386: 0.107
+kernel: 0.087
+mistranslation: 0.086
+boot: 0.081
+permissions: 0.072
+risc-v: 0.070
+performance: 0.068
+vnc: 0.067
+arm: 0.064
+network: 0.058
+assembly: 0.048
+hypervisor: 0.048
+user-level: 0.047
+debug: 0.047
+VMM: 0.041
+peripherals: 0.036
+virtual: 0.030
+TCG: 0.026
+KVM: 0.009
+
+Initial monitor does not output anything on Windows (MSYS2 binary)
+
+When running on Windows error messages before the UI is started are not showing up.
+
+For example when I run:
+
+qemu-system-i386.exe -L /mingw32/etc/qemu/ -m 20G
+
+It should display "ram size too large", according to gdb:
+
+Breakpoint 1, error_report (fmt=fmt@entry=0x71bdf6 <dma_aiocb_info+2426> "ram size too large") at C:/build/mingw/mingw-w64-qemu/src/qemu-2.4.0/util/qemu-error.c:233
+
+However the console does never receive that.
+
+As far as I could find out vfprintf is called, but it doesn't output anything.
+
+This affects both binary editions (for instance "qemu-system-i386.exe" AND "qemu-system-i386w.exe")
+
+dumpbin /all "C:\Program Files\qemu\qemu-system-i386.exe"|more
+Dump of file C:\Program Files\qemu\qemu-system-i386.exe
+PE signature found
+File Type: EXECUTABLE IMAGE
+FILE HEADER VALUES
+8664 machine (x64)
+
+This affects both binary editions (for instance "qemu-system-i386.exe" AND "qemu-system-i386w.exe")
+
+dumpbin /all "C:\Program Files\qemu\qemu-system-i386.exe"|more
+Dump of file C:\Program Files\qemu\qemu-system-i386.exe
+PE signature found
+File Type: EXECUTABLE IMAGE
+4.00 operating system version
+5.02 subsystem version: Win32
+
+
+
+Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+
+I just retested, it is fixed in the latest version on MSYS2.
+