Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06122 Crash/Freeze Critical (emulator) Always Jan 3, 2016, 06:26 Jan 5, 2016, 04:06
Tester B2K24 View Status Public Platform MESS (Official Binary)
Assigned To crazyc Resolution Fixed OS Windows Vista/7/8 (64-bit)
Status [?] Resolved Driver x68k.cpp
Version 0.169 Fixed in Version 0.170 Build 64-bit
Summary MESS-specific 06122: x68000 [ffight]: crashes with stack crawl
Description loading ffight from softlist results in crash with stack crawl right before the jump in-game

-----------------------------------------------------
Exception at EIP=000000000139136F (x68k_state::x68k_draw_gfx(bitmap_rgb32&, rectangle)+0x01ff): ACCESS VIOLATION
While attempting to read memory at 000000001B5F1000
-----------------------------------------------------
RAX=0000000000000000 RBX=000000000A1D80B0 RCX=00000000000003C0 RDX=00000000001007C0
RSI=000000000A54E1A0 RDI=00000000143D0080 RBP=000000000022A0F0 RSP=000000000022A070
 R8=00000000000003C0 R9=0000000000000401 R10=00000000000003E0 R11=000000001B3F0080
R12=0000000000000000 R13=0000000000000000 R14=000000000A54E1A0 R15=0000000000000002
-----------------------------------------------------
Stack crawl:
  000000000022A060: 000000000139136F (x68k_state::x68k_draw_gfx(bitmap_rgb32&, rectangle)+0x01ff)
  000000000022A1A0: 0000000001391C30 (x68k_state::screen_update_x68000(screen_device&, bitmap_rgb32&, rectangle const&)+0x04c0)
  000000000022A1F0: 000000000257D9FC (screen_device::update_partial(int)+0x011c)
  000000000022A250: 000000000138FAB0 (x68k_state::x68k_hsync(void*, int)+0x0210)
  000000000022A2A0: 0000000001389DA1 (x68k_state::device_timer(emu_timer&, unsigned int, int, void*)+0x01d1)
  000000000022A340: 000000000257B73D (device_scheduler::timeslice()+0x012d)
  000000000022A3A0: 000000000253B0F8 (running_machine::run(bool)+0x0148)
  000000000022F770: 000000000253609C (machine_manager::execute()+0x01fc)
  000000000022F950: 0000000002487599 (cli_frontend::execute(int, char**)+0x0839)
  000000000022FDF0: 00000000014F500B (utf8_main(int, char**)+0x016b)
  000000000022FE50: 000000000297311E (wmain+0x007e)
  000000000022FF20: 000000000040140C (__tmainCRTStartup+0x025c)
  000000000022FF50: 000000000040153B (mainCRTStartup+0x001b)
  000000000022FF80: 00000000777159DD (BaseThreadInitThunk+0x000d)
  000000000022FFD0: 000000007794A631 (RtlUserThreadStart+0x0021)
Steps To Reproduce mame64 x68000 ffight
Additional Information Tested 30 or 40 other games in driver randomly from software list and those didn't crash.
> Tafoid: Daily testing narrows this down to breaking sometime June 9/June 10, 2014 - specifically, this commit seems to be the suspected culprit: https://github.com/mamedev/mame/commit/c779d7a67f04698b182f892ca5895509bc8e2291
Flags
Regression Version 0.154
Affected Sets / Systems x68000 [ffight]
Attached Files
 
Relationships
There are no relationsihp linked to this issue.
Notes
5
User avatar
No.12319
Tafoid
Administrator
Jan 3, 2016, 18:46
First noted booting and playing in MESS 0.153 with failure/crash in 0.154.
User avatar
No.12320
mahlemiut
Developer
Jan 4, 2016, 00:36
Runs fine for me in current git code, maybe it's 32-bit specific?
User avatar
No.12321
B2K24
Moderator
Jan 4, 2016, 01:13
Perhaps it could be windows specific as I noted 64-bit build on this report.
User avatar
No.12322
mahlemiut
Developer
Jan 4, 2016, 02:06
Ok, I see that now. So, maybe win32/64 specific, since I'm using SDL.
User avatar
No.12326
crazyc
Developer
Jan 5, 2016, 04:06
Fixed in https://github.com/mamedev/mame/commit/134edd6d14d9dfb13ab4ca030edab336e863ea6a