Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06207 Crash/Freeze Minor Always May 6, 2016, 08:37 Dec 5, 2022, 05:26
Tester Beylie View Status Public Platform
Assigned To Resolution Invalid report OS Other
Status [?] Closed Driver
Version 0.173 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary MESS-specific 06207: nes [jparku]: jparku makes MAME 0.173 crash
Description Launching jparku makes MAME 0.173 crash. In 0.172 the same file launches without issue. Running Windows 10x64.
Steps To Reproduce Launching jparku via MAME 0.173
Additional Information
Github Commit
Flags
Regression Version 0.173
Affected Sets / Systems nes [jparku]
Attached Files
? file icon mame.ini (10,571 bytes) May 6, 2016, 14:07 Uploaded by Beylie
[Show Content]
Relationships
There are no relationship linked to this issue.
Notes
6
User avatar
No.12625
Beylie
Tester
May 6, 2016, 08:38
Not too sure what the severity on a crash like this should be. Please update accordingly.
User avatar
No.12626
Tafoid
Administrator
May 6, 2016, 09:58
I can't duplicate
Windows 7 - 64 bit - Binary from mamedev.org
I tried command line:
mame64 nes jparku
and also through the UI by simply launching MAME64, selecting the NES console, selecting the game from the software list.
Both times, I booted the game and was able to start and play without issue.

Your OS is listed other OTHER, I assume some flavor of Linux? Where did you get your distribution/binary?
User avatar
No.12627
Beylie
Tester
May 6, 2016, 13:28
Binary from the official site x64 version, downloaded this morning. The O/S is Windows 10 x64, not listed in the dropdown so I chose other. Let me try with x86 MAME.
User avatar
No.12628
Beylie
Tester
May 6, 2016, 13:30
I used the built-in gui to launch. When I use the command you used, I get this:

-----------------------------------------------------
Exception at EIP=0000000002A41758 (expression_validate(void*, char const*, expression_space)+0x0038): ACCESS VIOLATION
While attempting to read memory at 0000000000000030
-----------------------------------------------------
RAX=0000000000000000 RBX=000000000AA959A0 RCX=000000000AA587C0 RDX=00000000009E0047
RSI=000000000AA9AB26 RDI=000000000000000B RBP=0000000008A17FE0 RSP=0000000008A17FB0
 R8=0000000000161080 R9=0000000000000000 R10=0000000000000000 R11=0000000000000064
R12=0000000017E1A250 R13=000000000AA9AB10 R14=0000000002B0002A R15=0000000017E96B50
-----------------------------------------------------
Stack crawl:
  0000000008A17FB0: 0000000002A41758 (expression_validate(void*, char const*, expression_space)+0x0038)
  0000000008A18070: 0000000002A5DA36 (parsed_expression::parse_memory_operator(parsed_expression::parse_token&, char const*)+0x0146)
  0000000008A18130: 0000000002A61452 (parsed_expression::parse_symbol_or_number(parsed_expression::parse_token&, char const*&)+0x0162)
  0000000008A181B0: 0000000002A61CE6 (parsed_expression::parse_string_into_tokens()+0x0416)
  0000000008A18200: 0000000002A62431 (parsed_expression::parse(char const*)+0x00c1)
  0000000008A182B0: 00000000017FC327 (cheat_script::script_entry::script_entry(cheat_manager&, symbol_table&, char const*, xml_data_node&, bool)+0x0107)
  0000000008A18330: 00000000017FC8CC (cheat_script::cheat_script(cheat_manager&, symbol_table&, char const*, xml_data_node&)+0x016c)
  0000000008A18400: 00000000017FD1B2 (cheat_entry::cheat_entry(cheat_manager&, symbol_table&, char const*, xml_data_node&)+0x0352)
  0000000008A18630: 0000000001801F1A (cheat_manager::load_cheats(char const*)+0x022a)
  0000000008A188C0: 0000000001802732 (cheat_manager::reload()+0x05b2)
  0000000008A18970: 0000000001802991 (cheat_manager::cheat_manager(running_machine&)+0x0211)
  0000000008A189C0: 000000000178D86E (mame_machine_manager::create_custom(running_machine&)+0x002e)
  0000000008A18AA0: 00000000029D2B1D (running_machine::start()+0x0a5d)
  0000000008A18B00: 00000000029D2FFA (running_machine::run(bool)+0x00aa)
  0000000008A1F4F0: 000000000178F2FA (mame_machine_manager::execute()+0x015a)
  0000000008A1F960: 000000000180A9D2 (cli_frontend::execute(int, char**)+0x1092)
  0000000008A1F9D0: 000000000178E555 (emulator_info::start_frontend(emu_options&, osd_interface&, int, char**)+0x0035)
  0000000008A1FDF0: 00000000016F1834 (utf8_main(int, char**)+0x0124)
  0000000008A1FE50: 0000000002E9085F (wmain+0x007f)
  0000000008A1FF20: 000000000040140C (__tmainCRTStartup+0x025c)
  0000000008A1FF50: 000000000040153B (mainCRTStartup+0x001b)
  0000000008A1FF80: 00007FF9B9868102 (BaseThreadInitThunk+0x0022)
  0000000008A1FFD0: 00007FF9B9DBC5B4 (RtlUserThreadStart+0x0034)
User avatar
No.12629
Beylie
Tester
May 6, 2016, 13:41
edited on: May 6, 2016, 13:55
Seems the issue lies with the FE I used (Negatron). It modifies the mame.ini to add paths etc. If I used the mame.ini from the mame folder that this FE pointed to, it breaks. A new clean .ini fixes the issue. Thanks for taking the time to investigate. I've attached the mame.ini that breaks it. Odd that jpark loads fine, but jparku not. I'll take it up with the FE dev.
User avatar
No.12634
Tafoid
Administrator
May 7, 2016, 03:52
The stack crawl also indicates you have cheats enabled at runtime. When dealing with roms that don't load or crash, this should be the first thing you shut off.
Closing