Hi Dunrong,
I can't reproduce the segfault, but your patch still looks right to
me. Thanks!
Signed-of-by: Anthony Green gr...@moxielogic.com
AG
On Sat, Mar 30, 2013 at 9:35 PM, Dunrong Huang huan...@cloud-times.com wrote:
The value of do_interrupt member of CPUClass shoule be set to a
Am 31.03.2013 03:35, schrieb Dunrong Huang:
The value of do_interrupt member of CPUClass shoule be set to a
target-specific function, or it will lead to a segfault like below:
$ moxie-softmmu/qemu-system-moxie -M moxiesim
Segmentation fault
Cc: Anthony Green gr...@moxielogic.com
Cc: Blue
Thanks, applied.
On Sun, Mar 31, 2013 at 1:35 AM, Dunrong Huang huan...@cloud-times.com wrote:
The value of do_interrupt member of CPUClass shoule be set to a
target-specific function, or it will lead to a segfault like below:
$ moxie-softmmu/qemu-system-moxie -M moxiesim
Segmentation fault
Hi Andreas,
On Sun, Mar 31, 2013 at 1:01 PM, Andreas Färber afaer...@suse.de wrote:
That exception_index is used once from CPUMoxieState and once from
CPUState is telling me something is fishy here...
Are any test images available?
I have some basic RTEMS based test apps, but nothing that
Hi Anthony, thanks for your reply.
Below is the backtrace from core dump file, it may help.
$ moxie-softmmu/qemu-system-moxie -M moxiesim
Segmentation fault (core dumped)
$ gdb moxie-softmmu/qemu-system-moxie core
GNU gdb (Gentoo) 7.4.1
Copyright (C) 2012 Free Software Foundation, Inc.
License
The value of do_interrupt member of CPUClass shoule be set to a
target-specific function, or it will lead to a segfault like below:
$ moxie-softmmu/qemu-system-moxie -M moxiesim
Segmentation fault
Cc: Anthony Green gr...@moxielogic.com
Cc: Blue Swirl blauwir...@gmail.com
Cc: Andreas Färber
