Il 19/09/2013 10:11, Stefan Hajnoczi ha scritto:
> On Thu, Sep 19, 2013 at 8:36 AM, Taimoor Mirza wrote:
>
> Please use Reply-All to keep the CC list on your reply email. This
> way others on the mailing list can follow the discussion and
> participate.
>
>> O1 disassembly is at http://pastebin
On Thu, Sep 19, 2013 at 8:36 AM, Taimoor Mirza wrote:
Please use Reply-All to keep the CC list on your reply email. This
way others on the mailing list can follow the discussion and
participate.
> O1 disassembly is at http://pastebin.com/yxWAmmmf
>
> O2 disassembly is at http://pastebin.com/v0u
On Thu, Sep 05, 2013 at 04:02:43PM +0500, Taimoor Mirza wrote:
> I am using released 1.5.0 version from http://wiki.qemu.org/Download.
> I think it should be same as commit ID
> "295d81c62414a63c625fa2e78175573d4b3f5ba4"
>
> I have observed some interesting behavior. This problem does not come
> i
Hi Stefan,
I am using released 1.5.0 version from http://wiki.qemu.org/Download.
I think it should be same as commit ID
"295d81c62414a63c625fa2e78175573d4b3f5ba4"
I have observed some interesting behavior. This problem does not come
if I use MinGW with GCC version 4.7.2. I was originally using 4.
On Thu, Aug 29, 2013 at 12:10:48AM +0500, Taimoor Mirza wrote:
> Hi Stefan,
>
> Below is result of bt:
>
> Breakpoint 1, 0x006ac304 in abort ()
> (gdb) bt
> #0 0x006ac304 in abort ()
> #1 0x00553052 in _fu10846stack_chk_guard () at qemu-coroutine.c:111
> #2 0x0040d746 in _fu473stack_ch
Kindly ignore last email...it is reproducible on XP as well.
On Thu, Aug 29, 2013 at 11:31 AM, Taimoor Mirza wrote:
> I just tried it on Windows XP and its working fine there. So this
> problem comes only on Windows 7.
>
> -Taimoor
>
> On Thu, Aug 29, 2013 at 12:10 AM, Taimoor Mirza
> wrote
I just tried it on Windows XP and its working fine there. So this
problem comes only on Windows 7.
-Taimoor
On Thu, Aug 29, 2013 at 12:10 AM, Taimoor Mirza wrote:
> Hi Stefan,
>
> Below is result of bt:
>
> Breakpoint 1, 0x006ac304 in abort ()
> (gdb) bt
> #0 0x006ac304 in abort ()
> #1 0x0055
Hi Stefan,
Below is result of bt:
Breakpoint 1, 0x006ac304 in abort ()
(gdb) bt
#0 0x006ac304 in abort ()
#1 0x00553052 in _fu10846stack_chk_guard () at qemu-coroutine.c:111
#2 0x0040d746 in _fu473stack_chk_guard () at block.c:4294
#3 0x00413cc7 in _fu805stack_chk_guard () at bloc
On Wed, Aug 28, 2013 at 04:17:24PM +0500, Taimoor Mirza wrote:
> Thanks for your reply. Below are answers
>
> $ grep CONFIG_COROUTINE_BACKEND config-host.mak
> CONFIG_COROUTINE_BACKEND=win32
>
> (gdb) r
> Starting program: C:\tools\qemu\qemu-system-arm.exe
> -M realview-eb -m 256 -kernel Debug\\\
Hi Stefan,
Thanks for your reply. Below are answers
$ grep CONFIG_COROUTINE_BACKEND config-host.mak
CONFIG_COROUTINE_BACKEND=win32
(gdb) r
Starting program: C:\tools\qemu\qemu-system-arm.exe
-M realview-eb -m 256 -kernel DebugKD2.out -sd fat:16:rw:C:\\testCard
[New Thread 3836.0x404]
[New Th
On Wed, Aug 28, 2013 at 10:14:04AM +0500, Taimoor Mirza wrote:
> I am building QEMU on Windows using MinGW + Msys. If I build QEMU with
> Glib 2.28, qemu binary works fine for sdcard. I noticed that QEMU
> binary has dependency on libgthread-2.0-0.dll in this case.
> But when I build QEMU with Glib
Hi Guys,
I am building QEMU on Windows using MinGW + Msys. If I build QEMU with
Glib 2.28, qemu binary works fine for sdcard. I noticed that QEMU
binary has dependency on libgthread-2.0-0.dll in this case.
But when I build QEMU with Glib 2.33.8 version, its sdcard option
throw error at run time. A
12 matches
Mail list logo
