[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Bug 1182490] [NEW] [qemu-1.5] coroutine-win32.c broken
From: |
Dongsheng Song |
Subject: |
Re: [Qemu-devel] [Bug 1182490] [NEW] [qemu-1.5] coroutine-win32.c broken on NULL pointer |
Date: |
Thu, 23 May 2013 20:53:51 +0800 |
When I use qemu 1.4, it running smoothly:
SET PATH=E:\opt\qemu-1.4.1-win64
SET QEMU_LD_PREFIX=E:\opt\qemu-1.4.1-win64
E:\var\tmp\armhf_wheezy_qemu>qemu-system-arm -M vexpress-a9 -cpu
cortex-a9 -m 512 -uuid e04ec652-8bed-11e2-86b9-000c290c10de -drive
file=armhf_wheezy.img,if=sd,cache=writeback -kernel
vmlinuz-3.2.0-4-vexpress -initrd initrd.img-3.2.0-4-vexpress -append
"root=/dev/mmcblk0 rw init=/sbin/init"
On Thu, May 23, 2013 at 8:52 PM, Dongsheng Song
<address@hidden> wrote:
> Use rootfs download from
> https://i18n-zh.googlecode.com/files/armhf_wheezy_qemu_20130518.7z
>
> SET PATH=E:\opt\qemu-1.5.0-win64
> SET QEMU_LD_PREFIX=E:\opt\qemu-1.5.0-win64
>
> cd E:\var\tmp\armhf_wheezy_qemu
>
> E:\var\tmp\armhf_wheezy_qemu>qemu-system-arm -M vexpress-a9 -cpu
> cortex-a9 -m 512 -uuid e04ec652-8bed-11e2-86b9-000c290c10de -drive
> file=armhf_wheezy.img,if=sd,cache=writeback -kernel
> vmlinuz-3.2.0-4-vexpress -initrd initrd.img-3.2.0-4-vexpress -append
> "root=/dev/mmcblk0 rw init=/sbin/init"
>
> E:\var\tmp\armhf_wheezy_qemu>gdb qemu-system-arm
> (gdb) set args -M vexpress-a9 -cpu cortex-a9 -m 512 -uuid
> e04ec652-8bed-11e2-86b9-000c290c10de -drive
> file=armhf_wheezy.img,if=sd,cache=writeback -kernel
> vmlinuz-3.2.0-4-vexpress -initrd initrd.img-3.2.0-4-vexpress -append
> "root=/dev/mmcblk0 rw init=/sbin/init"
>
> (gdb) run
> Starting program: E:\opt\qemu-1.5.0-win64\qemu-system-arm.exe -M vexpress-a9
> -cp
> u cortex-a9 -m 512 -uuid e04ec652-8bed-11e2-86b9-000c290c10de -drive
> file=armhf_
> wheezy.img,if=sd,cache=writeback -kernel vmlinuz-3.2.0-4-vexpress -initrd
> initrd
> .img-3.2.0-4-vexpress -append "root=/dev/mmcblk0 rw init=/sbin/init"
> [New Thread 2164.0x480]
> [New Thread 2164.0x1ac]
> [New Thread 2164.0x162c]
> [New Thread 2164.0x514]
> [New Thread 2164.0xa6c]
> [New Thread 2164.0xc14]
> [New Thread 2164.0x854]
> [New Thread 2164.0xc1c]
> [New Thread 2164.0x169c]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 2164.0x162c]
> 0x000000000043e2cd in ?? ()
>
> On Thu, May 23, 2013 at 8:08 PM, Stefan Hajnoczi <address@hidden> wrote:
>> On Tue, May 21, 2013 at 02:11:05PM -0000, Cauchy Song wrote:
>>> Public bug reported:
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> [Switching to Thread 4340.0x163c]
>>> qemu_coroutine_switch (action=COROUTINE_TERMINATE, to_=0x0, from_=0x3ba1c80)
>>> at /home/cauchy/vcs/git/qemu/coroutine-win32.c:47
>>> (gdb) bt
>>> #0 qemu_coroutine_switch (action=COROUTINE_TERMINATE, to_=0x0,
>>> from_=0x3ba1c80) at /home/cauchy/vcs/git/qemu/coroutine-win32.c:47
>>> #1 coroutine_trampoline (co_=0x3ba1c80)
>>> at /home/cauchy/vcs/git/qemu/coroutine-win32.c:58
>>> #2 0x0000000077098fed in ?? ()
>>> #3 0x0000000000000000 in ?? ()
>>
>> What is the command-line?
>>
>> How do you reproduce the crash?
>>
>> Stefan
>>
[Prev in Thread] |
Current Thread |
[Next in Thread] |