On 24 November 2015 at 07:28, Franz-Josef Haider
<address@hidden> wrote:
On 11/23/2015 10:51 PM, Peter Maydell wrote:
(gdb) run cmaple
Starting program: /usr/bin/qemu-i386 cmaple
Program received signal SIGSEGV, Segmentation fault.
0x600104c0 in ?? ()
(gdb) info thread
Id Target Id Frame
* 1 LWP 18772 0x600104c0 in ?? ()
(gdb) thread apply all bt
Thread 1 (LWP 18772):
#0 0x600104c0 in ?? ()
#1 0x6029b37c in ?? ()
#2 0x6029b37c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
OK, that's definitely not the problem I thought it might have been.
Can you run maple under qemu, adding
-D qemu.log -d in_asm,out_asm,op,exec,int,cpu,guest_errors,unimp
on the command line?
That will create a (probably very large) qemu.log file (and
make qemu run rather slower while it's doing so). If you can
then put the log file up on some server somewhere I can have
a look at what is going on.
(I hope the logfile doesn't come out to be impracticably
large for this device but it might well do. If your access
to the device is via ssh or other terminal connection you
could also try not using the '-D' option, in which case the
log will go to stderr which you can capture on the local side
of your ssh connection.)
thanks
-- PMM