| 詳 細 | I just noticed this in MAME 0.113, when you reset the game (F3) it crashes MAME. However, if you hit reset during the POST (self test) screen or the region disclaimer (of which reset acts as a bypass) it works normally. However, once the 3D stuff starts, like the title screen and in-game, MAME locks up and eventually closes. First broke in 0.113.
Program received signal SIGSEGV, Segmentation fault.
0x00881168 in TransferDspData () at src/mame/drivers/namcos21.c:749
749 int primWords = (UINT16)
(pPointData[subAddr++]);
(gdb) bt full
#0 0x00881168 in TransferDspData () at src/mame/drivers/namcos21.c:749
primWords = 6376
subAddr = 16777116
len = 37711
masterAddr = 109295
i = 6376
code = 7542
pPointData = (const INT32 *) 0x594000c
pSource = (const UINT16 *) 0x6530a88
#1 0x008815cc in slave_port0_r (offset=0, mem_mask=0)
at src/mame/drivers/namcos21.c:881
result = 0
mem_mask = 0
#2 0x00e99261 in io_read_word_16be (address=0) at src/emu/memory.c:2826
entry = 74
#3 0x010f6fb8 in in () at src/emu/cpu/tms32025/tms32025.c:931
No locals.
#4 0x010f9b56 in tms32025_execute (cycles=40000)
at src/emu/cpu/tms32025/tms32025.c:2005
burn_cycles = 0
#5 0x00ea2c7d in cpunum_execute (cpunum=5, cycles=40000)
at src/emu/cpuintrf.c:1368
ran = -1283006294
#6 0x00eea642 in cpuexec_timeslice () at src/emu/cpuexec.c:504
target = {seconds = 42, subseconds = 22499999999998178}
base = {seconds = 42, subseconds = 20833333333331512}
cpunum = 5
ran = 39996
#7 0x00e81d29 in run_game (game=712) at src/emu/mame.c:347
settingsloaded = 0
machine = (running_machine *) 0x3f70078
error = 0
firstrun = 0
mame = (mame_private *) 0x3f7030c
cb = (callback_item *) 0x4
#8 0x00e3d678 in utf8_main (argc=2, argv=0x40804c0)
at src/osd/windows/winmain.c:194
result = 0
caps = {wPeriodMin = 1, wPeriodMax = 65535}
game_index = 712
ext = 0x266b7d4 ".map"
res = 0
#9 0x013814b1 in main (argc=2, a_argv=0x4080450) at src/osd/windows/main.c:67
i = 2
rc = 64290296
utf8_argv = (char **) 0x40804c0
argv = (TCHAR **) 0x4080450 |
その他
starblad - スターブレード (ST2, 海外版)