Sent: Saturday, April 01, 2006 6:54 AM André Braga wrote:
>Kazu, have you tested whether this avoids the hang (and 100% CPU time
>usage by QEMU, and being unable to kill the process by absolutely no
>means - Process Explorer's 'kill' included - other than rebooting) on
>WinXP host + kqemu and WinX
On 29 Mar 2006, at 11:33, Paul Brook wrote:
Also, the gcc -O2 option is more than the sum of the other options
it enables.
That, IMHO, is a bug. Of course, its not Qemu's bug. :-)
JP
--
"The New York Times is read by the people who run the country. The
Washington Post is read by the peop
Kazu, have you tested whether this avoids the hang (and 100% CPU time
usage by QEMU, and being unable to kill the process by absolutely no
means - Process Explorer's 'kill' included - other than rebooting) on
WinXP host + kqemu and WinXP guest when opening the guests' clock
application by double-cl
CVSROOT:/sources/qemu
Module name:qemu
Branch:
Changes by: Fabrice Bellard <[EMAIL PROTECTED]> 06/03/31 21:17:44
Modified files:
. : qemu-doc.texi
Log message:
update links
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/qemu-
Hi,
I still have problems with qemu-system-x86_64. Some programs crash some not. I
like to help to debug where I can. It seems to be distribution independent,
but I have separated and modified a SuSE10 x86_64 rescue image to reproduce
the errors (http://www.tbz-pariv.de/qemu/TestSuSE10x86_64.is
