 No.00835
aaron Developer
Apr 28, 2008, 20:04
|
There's really no solution for this. The cheat code is going through and accessing memory. Most memory accesses in MAME happen on the assumption that you are accessing it during execution. In this case, the read/write handler is calling cpu_spinuntil_int() which is only valid when you are executing. |
|---|---|
 No.00836
Tafoid Administrator
Apr 28, 2008, 20:11
|
Would it be safe to say this bug is one that should be labeled "Not Fixable" and resolved? Just trying to clean up some of the more generic bug reports - like this one. |
 No.00951
ShimaPong Tester
May 12, 2008, 18:43
edited on: May 12, 2008, 18:44
|
See driver/cps3.c.if (cpu_getexecutingcpu()>=0) // prevent cheat search crash..
if (activecpu_get_pc()==cps3_speedup_code_address) {cpu_spinuntil_int();return cps3_mainram[cps3_speedup_ram_address/4];}
This driver goes through this problem. If you delete it, this problem happens even in this driver.But I think it's too bad that update all drivers which use cpu_spinuntil_*(). I have added User Search Region for my WIP cheat engine. It supports Direct Memory Access and tries to read/write a memory directly (not use core read/write function). I have succeeds to search via this new search region system in taito_f3.c games without fatal error. In the future, I will list the drivers used cpu_spinuntil_*() and add auto setting as default at the initialization. NOTE : I don't know how to submit to official so check my WIP cheat engine thread (http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=147780&pag=0) |