qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 2/2] qemu-timer: move timeBeginPeriod/timeEndPer


From: Stefan Weil
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-timer: move timeBeginPeriod/timeEndPeriod to os-win32
Date: Thu, 21 Feb 2013 07:25:31 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2

Am 21.02.2013 00:49, schrieb Jacob Kroon:
> On Wed, Feb 20, 2013 at 9:46 PM, Jacob Kroon <address@hidden> wrote:
>> Paolo,
>>
>> Just a heads up, I tried the patched qemu (1+2+3) on my laptop at
>> home, which is running Windows 7 64-bit. I'm seeing qemu "lockups"
>> appearing randomly.. Will try to debug it.
>> On the other hand, plain vanilla 1.4.0 in Windows 7 seems to run fine
>> with my VxWorks image..
> So the problem seems to be related to wether I pass --enable-debug to
> qemu configure script.
> With debug enabled it runs fine in Windows 7 aswell. If I leave it out
> I get what appears to be a lockup
> a couple of seconds into the guest boot process. Best I could do for
> now was to attach to the process
> with gdb and get a backtrace:
>
> (gdb) bt
> #0  0x76fc000d in ntdll!LdrFindResource_U ()
>    from /cygdrive/c/Windows/SysWOW64/ntdll.dll
> #1  0x7704f896 in ntdll!RtlQueryTimeZoneInformation ()
>    from /cygdrive/c/Windows/SysWOW64/ntdll.dll
> #2  0x6ce2c99b in ?? ()
> #3  0x00000000 in ?? ()

The backtrace is usually better for QEMU with TCG interpreter. Run

     configure --enable-tcg-interpreter

The resulting binaries are much slower, but no longer create
code on the fly, so you get normal backtraces.

I also had to remove -fstack-protector-all (in file configure) to
get good backtraces for w32/w64.

Regards,

Stefan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]