just made a clean build out of the latest CVS source, still crashed
with the same backtrace. I suspect the opcode is too high. It's
eaxactly 32768, looks a bit suspicious to me. But what do I know
about CPU cores and opcodes ;)
> by just running it in xmame. it crashes immediately for me. I just
> checked out the latest CVS and I am about to do a new clean build.
>
> > gfire2 works here. How do you create the crash?
> >
> > On 3/1/06, Oliver Stöneberg <[EMAIL PROTECTED]> wrote:
> > > gfire2 crashes in xamem, but doesn't in official win32 MAME. Here is
> > > the backtrace:
> > >
> > > gram received signal SIGSEGV, Segmentation fault.
> > > 0x083db927 in cpu_readop (A=32768) at memory.h:1122
> > > 1122 INLINE UINT8 cpu_readop(offs_t A) { if
> > > (address_is_unsafe(A)) { memory_set_opbase(A); } return
> > > cpu_readop_unsafe(A); }
> > > (gdb) bt
> > > #0 0x083db927 in cpu_readop (A=32768) at memory.h:1122
> > > #1 0x083e6ac1 in op_c3 () at z180op.c:363
> > > #2 0x083eb406 in z180_execute (cycles=116665) at
> > > src/cpu/z180/z180.c:2066
> > > #3 0x0806ef90 in cpunum_execute (cpunum=0, cycles=116665) at
> > > src/cpuintrf.c:1485
> > > #4 0x0806a557 in cpu_timeslice () at src/cpuexec.c:1010
> > > #5 0x08069a80 in cpu_run () at src/cpuexec.c:451
> > > #6 0x080bc5d4 in run_game (game=5788) at src/mame.c:226
> > > #7 0x09c25334 in main (argc=4, argv=0xbfc01974) at
> > > src/unix/main.c:116
> > >
> > > _______________________________________________
> > > Xmame mailing list
> > > [email protected]
> > > http://toybox.twisted.org.uk/mailman/listinfo/xmame
> > >
> >
> > _______________________________________________
> > Xmame mailing list
> > [email protected]
> > http://toybox.twisted.org.uk/mailman/listinfo/xmame
>
>
>
> _______________________________________________
> Xmame mailing list
> [email protected]
> http://toybox.twisted.org.uk/mailman/listinfo/xmame
_______________________________________________
Xmame mailing list
[email protected]
http://toybox.twisted.org.uk/mailman/listinfo/xmame
