Julian Sikorski wrote:
Julian Sikorski napisał(a):
Lawrence Gold napisał(a):
On Nov 17, 2005, at 3:43 PM, Julian Sikorski wrote:
Did this crash occur in 0.101, or just since 0.101u5?
If you'd like to get u5, It is still mon mamedev.com:
http://mamedev.com/updates/0101u5_diff.zip
same as other u releases.
I looked at the diff for u5 in MESS CVS this morning, and it doesn't
seem the change should have any effect:
+#define _prefetch_m8abs(type, addr) \
+do { OP1(0x0f); OP1(0x18); MODRM_MABS(type, addr); } while (0)
+#define _prefetch_m8bd(type, base, disp) \
+do { OP1(0x0f); OP1(0x18); MODRM_MBD(type, base, disp); } while (0)
+
+
+
As far as I can tell, _prefetch_m8abs and _prefetch_m8bd aren't used
anywhere, unless through some macro magic that isn't apparent from a
casual glance. Have you tried reverting just the change to x86drc.h to
see if it fixes the crash?
_______________________________________________
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame
Hmm, something is wrong with my box rather than with mame. I have
compiled vanilla 0.101 just in case, but it segfaults with the same
backtrace. And I do remember myself checking model3 games after Aaron's
chages to memroy system in u1 and model3.c games were working. Now I
just have to figure out which update broke mame.
_______________________________________________
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame
I surrender :( I have no idea what might have broken drc cores. Any help
would be appreciated.
What hardware are you using and what version of Fedora are you running
exactly?
I myself have an x86_64 with both an x86_64 and an i386 version of
Rawhide installed I can try reproducing it. If I succeed its a Fedora
problem, if not it might be a hardware problem (which imho is more likely).
You could also try running memtest86 on your box, just leave it running
for a night. Another option is the old burnit kernel compile script
which compiles kernels non-stop and compares them to see if you've got
any hardware problems in my experience burnit is the best way to find
CPU/mem related problems. Dunno if burnit works 2ith the 2.6 kernel
otherwise just download an old kernel source tarball.
Regards,
Hans
_______________________________________________
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame
