Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05537 Multisession Critical (emulator) Always Apr 19, 2014, 20:26 Jun 11, 2014, 09:20
Tester haynor666 View Status Public Platform MAME (Official Binary)
Assigned To AWJ Resolution Fixed OS Windows Vista/7/8 (64-bit)
Status [?] Resolved Driver
Version 0.153 Fixed in Version 0.154 Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 05537: All namcos1.c sets: switching games from namcos1 driver in mame internal menu cause program to crash
Description When I try switch for example from blastoff to blazer I get:

-----------------------------------------------------
Exception at EIP=0000000000000000 (not found): ACCESS VIOLATION
While attempting to write memory at 0000000000000000
-----------------------------------------------------
RAX=0000000000000000 RBX=00000000113D0010 RCX=0000000000000000 RDX=00000000097CA
400
RSI=00000000113D260C RDI=00000000113D2604 RBP=0000000000227750 RSP=0000000000227
718
 R8=0000000000000000 R9=0000000000000000 R10=000000000677ECF0 R11=0000000000000
001
R12=000000000000C2D6 R13=0000000011024DA0 R14=000000000000C2D5 R15=F21F494C589C0
000
-----------------------------------------------------
Stack crawl:
  0000000000227710: 0000000000000000 (not found)
  0000000000227750: 0000000002BC7EA2 (not found)
  00000000002277E0: 0000000001655D13 (not found)
  00000000002278A0: 0000000001FF8E00 (not found)
  0000000000227A80: 000000000202E0BD (not found)
  000000000022F340: 0000000001F8D86C (not found)
  000000000022F870: 00000000020C770A (not found)
  000000000022FE00: 00000000015820C8 (not found)
  000000000022FE60: 000000000231A4DC (not found)
  000000000022FF20: 00000000004013F0 (not found)
  000000000022FF50: 00000000004014F8 (not found)
  000000000022FF80: 00000000773B652D (BaseThreadInitThunk+0x000d)
  000000000022FFD0: 0000000077AAC541 (RtlUserThreadStart+0x0021)
Steps To Reproduce just run any namcos1 game then select new game from the internal menu loading another or the same namcos1 set
Additional Information
Github Commit
Flags
Regression Version 0.153
Affected Sets / Systems All namcos1.c sets
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
3
User avatar
No.10598
AWJ
Developer
Apr 20, 2014, 00:04
Doesn't crash in 0.152. Suspect r29011. Tafoid?
User avatar
No.10599
B2K24
Senior Tester
Apr 20, 2014, 00:54
edited on: Apr 20, 2014, 00:59
I can confirm this behavior happens on occasion and which namcos1 games are loaded seems to not make any difference.

steps to reproduce the crash

- double click mame64.exe
- type faceoff or ws
- OK, OK
- TAB/Select New Game
- type faceoff or ws

You don't even need to change to different set to trigger this kind of crash.
User avatar
No.10600
B2K24
Senior Tester
Apr 20, 2014, 01:17
(gdb) bt
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

#0 0x0000000000000000 in ?? ()
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

#1 0x00000000041e0daa in delegate_base<void, address_space&, unsigned int, unsi
gned char, unsigned char, _noparam, _noparam, _noparam, _noparam, _noparam, _nop
aram, _noparam, _noparam>::operator() (this=0x31aa88, p1=..., p2=0,
    p3=0 '\000', p4=255 'ÿ') at src/emu/delegate.h:652
#2 0x0000000003aba0ef in namcos1_state::bank_w (this=0x2f5fc8, space=...,
    offset=0, data=0 '\000', bank=0) at src/mame/machine/namcos1.c:38
#3 0x0000000001196565 in namcos1_state::bank1_w (this=0x2f5fc8, space=...,
    offset=0, data=0 '\000', mem_mask=255 'ÿ')
    at src/mame/machine/namcos1.c:41
#4 0x00000000041e0daa in delegate_base<void, address_space&, unsigned int, unsi
gned char, unsigned char, _noparam, _noparam, _noparam, _noparam, _noparam, _nop
aram, _noparam, _noparam>::operator() (this=0x5216d8a0, p1=..., p2=0,
    p3=0 '\000', p4=255 'ÿ') at src/emu/delegate.h:652
#5 0x00000000042237c8 in handler_entry_write::write8 (this=0x5216d7e8,
    space=..., offset=0, data=0 '\000', mask=255 'ÿ') at src/emu/memory.c:480
#6 0x000000000400c922 in address_space_specific<unsigned char, (endianness_t)1,
 false>::write_native (this=0x513de1a8, offset=0, data=0 '\000')
    at src/emu/memory.c:1202
#7 0x000000000400b6ea in address_space_specific<unsigned char, (endianness_t)1,
 false>::write_byte (this=0x513de1a8, address=0, data=0 '\000')
    at src/emu/memory.c:1487
#8 0x00000000021a25ca in write_memory (data=0 '\000', address=0,
    this=0x33ca48) at src/emu/cpu/m6809/m6809.h:152
#9 write_operand (data=0 '\000', ordinal=0, this=0x33ca48)
    at src/emu/cpu/m6809/m6809inl.h:120
#10 execute_one (this=0x33ca48) at obj/windows64d/emu/cpu/m6809/m6809.inc:1158
#11 m6809_base_device::execute_run (this=0x33ca48)
    at src/emu/cpu/m6809/m6809.c:535
#12 0x0000000004045382 in device_execute_interface::run (this=0x33cef8)
    at src/emu/diexec.h:187
#13 0x0000000002d6ba00 in device_scheduler::timeslice (this=0x22e4b8)
    at src/emu/schedule.c:474
#14 0x0000000000000000 in ?? ()
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)