[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1528718] Re: Initial monitor does not output anything
From: |
ECC_OK |
Subject: |
[Qemu-devel] [Bug 1528718] Re: Initial monitor does not output anything on Windows (MSYS2 binary) |
Date: |
Tue, 10 May 2016 17:49:15 -0000 |
** Description changed:
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 (address@hidden <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.
+
+ Maybe the binary is build for the "win32" subsystem which does not have
+ a console window attached by default?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1528718
Title:
Initial monitor does not output anything on Windows (MSYS2 binary)
Status in QEMU:
New
Bug description:
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 (address@hidden
<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.
Maybe the binary is build for the "win32" subsystem which does not
have a console window attached by default?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1528718/+subscriptions
- [Qemu-devel] [Bug 1528718] Re: Initial monitor does not output anything on Windows (MSYS2 binary),
ECC_OK <=