|
|
Joined: Mar 2013
Posts: 81
Member
|
OP
Member
Joined: Mar 2013
Posts: 81 |
I'm using SDLMAME 0261 and the debugger will not open any more after it randomly crashed today. I had the same thing happen on an earlier version and cannot get the debugger to open in that version either now. I'm using 0261 as that's the last version available for my Intel Mac from the SDLMAME site. The error I get at the terminal is: 2024-11-12 15:12:38.006 mame[1728:17336] *** Assertion failure in -[NSPopUpButton initWithFrame:], /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1894.70.110/AppKit.subproj/NSView.m:1352
Caught unhandled exception
zsh: segmentation fault ./mame goldnaxe -debug I am fairly savvy with Macs but I have no idea what's caused this or what the fix is. I know that apps sometimes won't open if they've written a temporary file somewhere and then crashed without deleting the temporary file, so I'm assuming that might be the case here. MAME itself runs, just not the debugger. Thank you for any help or suggestions.
|
|
|
|
|
Joined: Mar 2001
Posts: 17,234 Likes: 259
Very Senior Member
|
Very Senior Member
Joined: Mar 2001
Posts: 17,234 Likes: 259 |
That was a common issue with older versions of MAME (on all systems, incidentally) but I haven't seen it in a long time.
The usual fix is simply to run MAME for the same game without -debug once, and that should clear the corrupted saved debugger settings.
|
|
|
|
|
Joined: Mar 2013
Posts: 81
Member
|
|
OP
Member
Joined: Mar 2013
Posts: 81 |
Thank you. Do you know where the debugger settings might be saved? I tried to open the same game with ./mame goldnaxe and just get a blank screen now and have to force-quit it. Opening it in a window works ok though and I get a "The last time you opened MAME, it unexpectedly quit..." message but doesn't seem to fix the problem with the debugger. I'm assuming macOS is trying to restore the state of the windows but something is stopping it from doing that.
|
|
|
|
|
Joined: Mar 2001
Posts: 17,234 Likes: 259
Very Senior Member
|
|
Very Senior Member
Joined: Mar 2001
Posts: 17,234 Likes: 259 |
That's definitely great, but I don't think compiling is OP's problem.
|
|
|
|
|
Joined: Mar 2001
Posts: 17,234 Likes: 259
Very Senior Member
|
|
Very Senior Member
Joined: Mar 2001
Posts: 17,234 Likes: 259 |
I think the debugger settings are in the game's .cfg file.
|
|
|
|
|
Joined: Mar 2013
Posts: 81
Member
|
|
OP
Member
Joined: Mar 2013
Posts: 81 |
Perfect, it's working again now. Thank you very much. Sorry I didn't think to check that, I guess I was expecting the debugger settings to be stored in ~/Library/Caches or Application Support or somewhere like that.
Hairball - thanks for the Intel builds, I'll check them out later.
|
|
|
|
|
Joined: Feb 2004
Posts: 2,603 Likes: 307
Very Senior Member
|
|
Very Senior Member
Joined: Feb 2004
Posts: 2,603 Likes: 307 |
I think the debugger settings are in the game's .cfg file. Correct, it’s in the .cfg file. You can nuke the <debugger> node (and all its child nodes) to clear out the debugger settings. If you can make 0.271 crash like this, please give me the errant .cfg file and if possible also catch the unhandled exception in a debugger (e.g. gdb or lldb) so I can try to fix it.
|
|
|
|
|
Joined: Mar 2013
Posts: 81
Member
|
|
OP
Member
Joined: Mar 2013
Posts: 81 |
It crashed again today in my 0271 build on macOS 10.15.7. I just built this version on my machine and had to apply a patch to fix the issue with BGFX, but it seems to work fine. Prior to this I was using the debugger and closed it before I switched off my machine, but the debugger didn't crash at that point. The .cfg file looks like this:
<?xml version="1.0"?>
<!-- This file is autogenerated; comments and unknown tags will be stripped -->
<mameconfig version="10">
<system name="goldnaxe">
<counters>
<coins index="0" number="25" />
</counters>
<debugger>
<window position_x="348.000000" position_y="60.000000" size_x="932.000000" size_y="512.000000" type="1" rightbar="1">
<splits state="174.000000" disassembly="242.000000" />
<selection visible="0" start_x="0" start_y="0" />
<scroll position_x="0.000000" position_y="0.000000" />
<history />
</window>
<window position_x="12.000000" position_y="221.000000" size_x="693.000000" size_y="548.000000" type="3" cpu="0" rightbar="1">
<expression>
3627
</expression>
<history>
<item>
3627
</item>
</history>
<selection visible="0" start_x="66" start_y="10" />
<scroll position_x="0.000000" position_y="0.000000" />
</window>
</debugger>
<ui_warnings launched="1731528171" warned="1731528171" />
</system>
</mameconfig>
This is the output I got from lldb - I had to restart my machine because it looks MAME tried to open in fullscreen mode initially and I just got a blank screen and couldn't force-quit it: % lldb ./mame goldnaxe -debug
(lldb) target create "./mame"
Current executable set to '/Users/mac/Downloads/mame-mame0271/mame' (x86_64).
(lldb) settings set -- target.run-args "goldnaxe"
(lldb) run
Process 577 launched: '/Users/mac/Downloads/mame-mame0271/mame' (x86_64)
2024-11-15 15:18:32.376752+0000 mame[577:7562] [plugin] AddInstanceForFactory: No factory registered for id <CFUUID 0x118747d30> F8BB1C28-BAE8-11D6-9C31-00039315CD46
2024-11-15 15:18:32.405095+0000 mame[577:7562] HALC_ShellDriverPlugIn::Open: Can't get a pointer to the Open routine
2024-11-15 15:18:32.406048+0000 mame[577:7562] HALC_ShellDriverPlugIn::Open: Can't get a pointer to the Open routine
Process 577 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGTERM
frame #0: 0x00007fff70685dea libsystem_kernel.dylib`mach_msg_trap + 10
libsystem_kernel.dylib`mach_msg_trap:
-> 0x7fff70685dea <+10>: retq
0x7fff70685deb <+11>: nop
libsystem_kernel.dylib`mach_msg_overwrite_trap:
0x7fff70685dec <+0>: movq %rcx, %r10
0x7fff70685def <+3>: movl $0x1000020, %eax ; imm = 0x1000020
Target 0: (mame) stopped.
|
|
|
|
|
Joined: Mar 2013
Posts: 81
Member
|
|
OP
Member
Joined: Mar 2013
Posts: 81 |
I realised after I posted yesterday that I wasn't running the lldb command correctly because it wasn't passing all of the arguments supplied to MAME. Using lldb ./mame -- goldnaxe -debug I get the following output from lldb: (lldb) target create "./mame"
Current executable set to '/Users/mac/Downloads/mame-mame0271/mame' (x86_64).
(lldb) settings set -- target.run-args "goldnaxe" "-debug"
(lldb) run
Process 594 launched: '/Users/mac/Downloads/mame-mame0271/mame' (x86_64)
2024-11-16 11:10:14.750263+0000 mame[594:8708] [plugin] AddInstanceForFactory: No factory registered for id <CFUUID 0x1186b4f00> F8BB1C28-BAE8-11D6-9C31-00039315CD46
2024-11-16 11:10:14.780917+0000 mame[594:8708] HALC_ShellDriverPlugIn::Open: Can't get a pointer to the Open routine
2024-11-16 11:10:14.782160+0000 mame[594:8708] HALC_ShellDriverPlugIn::Open: Can't get a pointer to the Open routine
2024-11-16 11:10:16.613622+0000 mame[594:8708] *** Assertion failure in -[NSPopUpButton initWithFrame:], /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1894.70.110/AppKit.subproj/NSView.m:1352
Caught unhandled exception
Process 594 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
frame #0: 0x0000000107f81fb4 mame`device_debug::compute_debug_flags() + 4
mame`device_debug::compute_debug_flags:
-> 0x107f81fb4 <+4>: movq (%rdi), %rax
0x107f81fb7 <+7>: movq 0xd0(%rax), %rax
0x107f81fbe <+14>: movq 0x98(%rax), %rcx
0x107f81fc5 <+21>: movq 0x10(%rcx), %r8
Target 0: (mame) stopped.
(lldb) thread backtrace
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
* frame #0: 0x0000000107f81fb4 mame`device_debug::compute_debug_flags() + 4
frame #1: 0x0000000107f83d67 mame`device_debug::~device_debug() + 87
frame #2: 0x000000010b94be5f mame`device_t::stop() + 95
frame #3: 0x00000001090d1220 mame`running_machine::stop_all_devices() + 80
frame #4: 0x00000001090d1c2a mame`running_machine::run(bool) + 1114
frame #5: 0x0000000103fc8fc9 mame`mame_machine_manager::execute() + 569
frame #6: 0x0000000103a7e0d2 mame`cli_frontend::start_execution(mame_machine_manager*, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) + 578
frame #7: 0x0000000103a7fccd mame`cli_frontend::execute(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >&) + 77
frame #8: 0x0000000103fca54b mame`emulator_info::start_frontend(emu_options&, osd_interface&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >&) + 43
frame #9: 0x000000010928b4d8 mame`main + 168
frame #10: 0x00007fff6f257cc9 libdyld.dylib`start + 1
|
|
|
|
1 members (Stick),
219
guests, and
1
robot. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
Forums9
Topics9,328
Posts122,128
Members5,074
| |
Most Online1,283
Dec 21st, 2022
|
|
These forums are sponsored by Superior Solitaire, an ad-free card game collection for macOS and iOS. Download it today!
|
|
|
|
