Follow me on twitter for up to the minute release updates: @sdlmame_osx

Prerequisites for using the MAME console application on MacOS:

  • Intel-based Macs – MacOS 10.14 or above (majority of Macs made before 2021).
  • Apple Silicon (aarch64)-based Macs – MacOS 12.0 “Monterey”.
  • libSDL 2.0 or above – SDL for MacOS (currently 2.26.3). Always get the latest release!
  • Knowledge of using the within MacOS or a frontend.
  • Disable Gatekeeper!

The current MAME release is 0.252, released on February 21st, 2023.

All old releases are archived here.

55 thoughts on “Main

    1. Hola!! me podríais indicar cómo se inicia la carpeta de mame que me he descargado en Mac por favor? no sé cómo ejecutarlo!! gracias

  1. It would be helpful to add links to the latest version of MAME per MacOS.

    Example: MacOS 10.14 or above = MAME 0.244
    MacOS 10.13 = MAME 0.???
    MacOS 10.12 = MAME 0.???
    MacOS 10.11 = MAME 0.???
    MacOS 10.10 = MAME 0.???
    MacOS 10.9 = MAME 0.???

    1. I like this idea but I didn’t keep those records and even I didn’t retain all this data. A good way to gauge this is looking up the version release date and then look up what MacOS was available at that time for a decent gauge. Usually I built on the oldest OS X possible to retain as much compatibility as I could. Still, I’ll see what I can come up with when I have some time!

  2. MAME 0.244 needs actually macOS 12 (Monterey) to run.

    When I try to run it on macOS 11 (Big Sur) it is not working.
    See message when I try to run it under Big Sur:
    user@Mac /Applications/mame0244-arm64 $ ./mame
    dyld: Symbol not found: __ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv
    Referenced from: /Applications/mame0244-arm64/./mame (which was built for Mac OS X 12.0)
    Expected in: /usr/lib/libc++.1.dylib

      1. Thank you so much. I am also getting a crash when I try to run SDL MAME version 0.244 on Mac OS 11 Big Sur. A fix for this would be super useful because I can’t go up to Mac OS 12 just yet.

        1. More details: Running the file “mame64” results in a crash, running the file “mame” succeeds. MacOS 11 Big Sur.

          1. The only file you should have as a executable is “mame”, the former “mame64” pre-dates the M1 processors and the zip only comes with a “mame” executable. If you have just placed new releases over old ones, it never would have deleted the old “mame64”, but that is surely over 2 years old, and isn’t supposed to run on M1. If the “mame” file runs on Big Sur then all should be well, but I can’t test that. If it doesn’t run, mame is also available through macports and brew and should work on Big Sur.

  3. Hi,
    do you know if there is a way to have a shortcut to start the app from the dock? Using maybe a command or something similar to bypass the terminal and start SDL MAME easier?
    Thank you for your efforts on MAME dev

    1. I’m personally unsure if you can add the MAME binary to the Dock directly, but if you can, you may have to keep all the corresponding MAME folders in your Home directory. Give it a try and see what happens!

      1. Last I recall that app had no new development in years. Just by having to rename the mame binary tells me it’s been a few years it’s been dead already. I don’t suggest or recommend people use dead software to do things with. It can’t possibly support new things added to mame only very basic things it can interpret.

      1. What is the correct way to open sdlmame? What’s the right command to do (I know it’s possible to double click the mame64 file to open, isn’t it right?).
        Do you also know if there is a way to do an apple script for this terminal command and save it as an app?


    2. Typically, you can run any script by double click in the Finder or click in the dock simply by changing the script’s filename extension from, say, .sh to .command.

  4. I’ve used it for a few years with no problems. I agree with your comment about “dead software” however, this app just executes the mame executable and nothing else. It doesn’t use or enhance any mame features. If you want to give it a shot without renaming your mame executable, right click on the M64 app and show package contents. Go to the Contents/Resources directory and edit the script file changing mame64 to mame. Save it then move the into your mame directory. Can’t quite remember but I think everytime you update mame you need to run it from the terminal once.

  5. Not working on Mac Os Monterey, when running “./mame” command into the terminal, the screen goes black, mouse pointer is displayed and responding, BUT, nothing else works, backlit keyboard or screen bright keys are working, but trying to go back, change or go to any other app, nothing works, only mouse pointer, I had to force shutdown by pressing power btn, that was the only way out. Fyi I installed LibSDL (copied the content into /Library/Frameworks).

    Any ideas?

    1. First run should be “./mame -cc” for “create config”. After just the main command will do. Also, there is a delay the first time mame is run, I believe it is building database data, where the screen will appear unresponsive and stay black. This is normal and mame will start, let it finish.

    2. you don’t have to “slam” down or force the power off FYI. Just hit Command-Option-esc and you can force quit/or relaunch the terminal from there. 🙂

  6. it gives me every time this error, SDL is installed correctly.
    MacOS Ventura 13 last beta

    dyld[4591]: Library not loaded: @rpath/SDL2.framework/Versions/A/SDL2
    Referenced from: /Volumes/Saveria/Archivio/Arcade/Mame/mame
    Reason: tried: ‘/System/Volumes/Preboot/Cryptexes/OS@rpath/SDL2.framework/Versions/A/SDL2’ (no such file), ‘/Library/Frameworks/SDL2.framework/Versions/A/SDL2’ (no such file), ‘/System/Library/Frameworks/SDL2.framework/Versions/A/SDL2’ (no such file, not in dyld cache)


    1. Unfortunately, I cannot provide help for a beta. We don’t target beta OS releases and it is generally poor form to post a bug report for running something on a beta OS. You are on your own with betas. There is no guarantee anything works or what Apple has changed in order for programs and libraries to operate correctly. When the OS is released the team will likely have support for it soon after but generally not before.

    2. Because it’s beta OS. Mine runs fine in Monterey but also tried in Ventura and it doesn’t. It’ll prob be fixed when Ventura is an official release or shortly after via an update to Ventura if the initial release doesn’t work. Just install Monterey into a new container and run it there. I keep Monterey as my primary OS and run Ventura latest dev beta in a container as a secondary OS to boot into to try apps and such, but never rely on it for daily use.

  7. First off, Thank you, this is amazing! Thank you!


    When I try to launch any game file it says “Required rom/system files for this select system are missing etc. etc.” Last time I installed this project I simply put the entire folder in my Apps directory on my Monterey MacOS M1 Pro 14″ and put the roms collection I have all in the roms folder and launched it and played several games without error. I just reinstalled this on my machine after leaving Ventura beta some I’m official on Monterey. I did put the SDL2.framework into the frameworks folder before launching it and get no errors in the terminal when launching. The Mame window comes up just fine and then I get the above error when opening any rom (or trying to). I know I’m probably missing a step somewhere but last time it just worked…Advice? Thanks a million.

    1. The roms won’t even show up in my Available tabs.
      I tried to manually open my rom, which is a Neogeo game, and still “Required rom/system files for this select system are missing etc. etc.” error showed up. I did everything as instructed, had the required bios and rom.

      Did you manage to successfully run a game in MAME?

    1. The “endings” file shouldn’t be needed in this day and age. The source can be pulled from GitHub or even one of the pre made zip files as well on mamedev. There is a guide on their docs site with some more up to date information: For something as old as .223 you can skip the python3 install, as it uses what MacOS already had back then. The only specifics I can think of is to throw the make command a “-j{insert proc core +1} to speed up compilation by using all your cores available. It should build out of the box, though may not on a newer MacOS release. I also keep builds of older releases available here: if you don’t want to bother with setting up all that. Good luck!

  8. HI there Jay;
    I have the Mame emulator working on Monteray 12.6. I can’t get any roms to work though? I know the versions are important when it comes to the age of Roms. My latest try was with version .243 and the .243 roms won’t work?
    Any help much appreciated?

  9. Thanks for doing the compile for Mac!
    Although it seems like the 0.248 version is ready, the link seems to be broken.
    Is there a compiled 0.248 version for Mac available?

  10. Hi,

    Great job with the latest update.

    Have you had any feedback regarding IMGTOOL issues?

    I am having trouble installing and using IMGTOOL on a Mac M1 Monterey.


    1. There used to be a few out there, and may still be. “M2” was one many used, not sure on its status these days. Most prefer the GUI within mame, it covers all the options, can handle screenshots, filters and more. It’s what I would recommend to use but it’s not very Mac-like.

  11. Hi! I would like to know what’s the best way to update SDLmame with new versions. Is it ok to keep my folders (with Roms files into rom folder/ and also artwork files and saved config) and just overwrite all te exec new files?

    1. Personally, I would overwrite any files contained in the zip. There are files in the xml directories that control console/computer emulation information that if not updated for long periods will not operate correctly. Basically, outside of the dir.txt files, if it ships in the zip, overwrite it. The zip will never contain anything that would overwrite your roms, etc.

      Just be careful on MacOS Finder, it will overwrite directories with empty contents in some uses.

      1. Ok thanks for the tip.
        So in the case that I’ve inserted all my Roms in the rom folder under the zip extraction, if I’ll take all, copy and paste, this means that for that folder, I need to merge the two (or not copy it and ignore), am I right?

        1. Yes. Though tbh I’d avoid any insertions from the zip file into the roms folder. All that will ever be there is the dir.txt to ensure the directory is created properly when unzipped. You don’t need the txt file for mame to function. Just be careful with folders you want to keep the contents of, a better solution is moving your files into the created folders after unzipping. Whatever you do, make sure the roms folder is intact afterwards!

          1. So I’ll not copy at all (rom “ or artwork folders, for example). The last question is: what about all the config I did? Like the language selection or the audio/video/controllers and key config? Are there any problems with this if I copy and overwrite all the folders and file within the zip?

          2. Any files you’ve created, saving controller profiles, video settings, game settings, etc should not be overwritten by the zip file. If you do choose to remove them you will have to setup devices and such again, which is usually the opposite of what one would normally like. In order for those per-game settings to be carried over the cfg files must remain. But again, all that’s shipped is a dir.txt to create the directory so you should be safe when updating.

    1. I have yet to update personally. I have no idea why you wouldn’t be able to load anything. Try checking gatekeeper, make sure it’s off or mame is allowed to run and read dirs, outside of that, I’m not sure.

  12. Hello,

    I haven’t used MAME in over 10 years and a lot has changed. I’m currently running an M1 Mac with Monterey. Just downloaded the latest version you have and I can’t open the mame file, it shows up as a terminal app and the OS forbids me from opening the program. Do you have a “Read Me” or info section I can review to teach myself what I need to do to run the program?

    Thanks for your work,

    1. This port of mame behaves just like the Windows counterpart, being that it’s run from the command line (terminal) on MacOS. Functionality, is 100% just like it is on Windows machines as a result of the porting to the sdl library, as such, the documents at should be adequate for the operation of the program.
      The only roadblock on MacOS is the “Gatekeeper” system which blocks things downloaded from the internet from running (unless I buy a Apple Developer account and pay them yearly) but it can be disabled by users, or mame can be permitted to run through it. Check this link for some instructions on disabling the feature to enable mame to run.
      Afterward, please note mame must be run from the MacOS Terminal to ensure it sets the environment correctly. Your first operation should be to create the config “./mame -cc” will do that and than you can just run “./mame” from within the directory. Changing dirs acts the same as Windows for the most part but there are differences on Unix based systems such as MacOS.

      1. Hi Jay,
        the command “./mame -cc” must be started every time or just the first time opening mame?
        And after updating mame (unzipping and overwriting all the folders and files in your file) it is necessary?


        1. Hi! I would suggest running that command on a new install, or even one that you may have changed defaults and things are acting strange on. If all is well after an update, no need to run it again.

  13. Like another user posted already, I’m occasionally getting hard crashes when launching that render the entire system unusable (although in my case, the mouse is also unresponsive. I even left it on overnight to see if it would recover (it did not).

    It only happens about 50% of the time. The only pattern seems to be that it doesn’t happen the first time after the system has been rebooted. mame -cc was run and gatekeeper has been disabled.

    Running 0.251 with SDL2 Framework version 2.26.3 on latest release version of Ventura and M2 Pro.

    1. Hrm I have not seen it had any reports of this happening. But the M2 is new so it might be an incompatibility with the XCode version I’m using. A new release should be out next week so right now waiting may be your best option. You can use the Intel build with Rosetta, that may eliminate the random freezes. Though to me, it sounds gatekeeper related, even though you’ve turned it off. That’s exactly what happens when gatekeeper blocks mame as well. Could very well be a Ventura bug. Try the Intel build, it may prove to be arm specific issue here. Do you have any log or error report?

      1. Ok so this is interesting…

        0) I double-checked that gatekeeper was disabled. Check.
        1) To confirm, I’ve not found anything useful in the logs.
        2) I was able to run the arm versions 5 times in quick succession; crashed on the 6th attempt.
        3) I downgraded to v2.26.1 of the framework (as that’s the version noted above). Crashed the first time.
        4) Downloaded and ran the Intel version. Also crashes (every time).

        Version of Ventura (so there’s no doubt) is 13.2.1. It’s also a brand new machine and the only other things installed on it are Steam and Crossover.

        Feel free to reach out via email if you want to have a side discussion.

  14. I’m on Mac OS Ventura 13.2.1
    I downloaded MAME 0.251 and when I launch it via the terminal, my screen goes black and it stays like that, nothing happens 🙁

    When I exit (ESC) I get an error report “name quit unexpectedly”

    Translated Report (Full Report Below)

    Process: mame [72336]
    Path: /Applications/mame0251-x86/mame
    Identifier: mame
    Version: ???
    Code Type: X86-64 (Native)
    Parent Process: zsh [72314]
    Responsible: iTerm2 [1909]
    User ID: 501

    Date/Time: 2023-02-17 22:37:36.3962 +1100
    OS Version: macOS 13.2.1 (22D68)
    Report Version: 12
    Bridge OS Version: 7.2 (20P3045)
    Anonymous UUID: 93F8781C-2BA7-3EAF-76AB-AB59F1E9E477

    Sleep/Wake UUID: 5CE85C33-6A95-4DD6-BD00-68B1A014B459

    Time Awake Since Boot: 160000 seconds
    Time Since Wake: 1144 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0 Dispatch queue:

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000001a517c8
    Exception Codes: 0x0000000000000001, 0x0000000001a517c8

    Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
    Terminating Process: exc handler [72336]

    VM Region Info: 0x1a517c8 is not in any region. Bytes before following region: 4513982520
    __TEXT 10eb30000-11ab80000 [192.3M] r-x/r-x SM=COW …0251-x86/mame

    Thread 0 Crashed:: Dispatch queue:
    0 mame 0x117481123 0x10eb30000 + 143986979
    1 mame 0x11688d027 0x10eb30000 + 131452967
    2 mame 0x11688d34e 0x10eb30000 + 131453774
    3 mame 0x1168ce0ac 0x10eb30000 + 131719340
    4 mame 0x11683585e 0x10eb30000 + 131094622
    5 libsystem_c.dylib 0x7ff814dd4c1f __cxa_finalize_ranges + 409
    6 libsystem_c.dylib 0x7ff814dd4a39 exit + 35
    7 mame 0x1168c71b0 0x10eb30000 + 131690928
    8 dyld 0x7ff814bab310 start + 2432

    Thread 1:
    0 libsystem_pthread.dylib 0x7ff814ed9c58 start_wqthread + 0

    Thread 2:
    0 libsystem_pthread.dylib 0x7ff814ed9c58 start_wqthread + 0

    Thread 3:
    0 libsystem_pthread.dylib 0x7ff814ed9c58 start_wqthread + 0

    Thread 4:: caulk.messenger.shared:17
    0 libsystem_kernel.dylib 0x7ff814e9f53e semaphore_wait_trap + 10
    1 caulk 0x7ff81e6518f8 caulk::mach::semaphore::wait_or_error() + 16
    2 caulk 0x7ff81e637664 caulk::concurrent::details::worker_thread::run() + 36
    3 caulk 0x7ff81e637328 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple > >(void*) + 41
    4 libsystem_pthread.dylib 0x7ff814ede259 _pthread_start + 125
    5 libsystem_pthread.dylib 0x7ff814ed9c7b thread_start + 15

    Thread 5:
    0 libsystem_kernel.dylib 0x7ff814e9f5c2 mach_msg2_trap + 10
    1 libsystem_kernel.dylib 0x7ff814ead604 mach_msg2_internal + 82
    2 libsystem_kernel.dylib 0x7ff814ea6635 mach_msg_overwrite + 723
    3 libsystem_kernel.dylib 0x7ff814e9f8a8 mach_msg + 19
    4 CoreMIDI 0x7ff82ce21600 XServerMachPort::ReceiveMessage(int&, void*, int&) + 94
    5 CoreMIDI 0x7ff82ce52bc7 MIDIProcess::MIDIInPortThread::Run() + 105
    6 CoreMIDI 0x7ff82ce3ad40 XThread::RunHelper(void*) + 10
    7 CoreMIDI 0x7ff82ce3bfb3 CAPThread::Entry(CAPThread*) + 77
    8 libsystem_pthread.dylib 0x7ff814ede259 _pthread_start + 125
    9 libsystem_pthread.dylib 0x7ff814ed9c7b thread_start + 15

    Thread 6::
    0 libsystem_kernel.dylib 0x7ff814e9f5c2 mach_msg2_trap + 10
    1 libsystem_kernel.dylib 0x7ff814ead604 mach_msg2_internal + 82
    2 libsystem_kernel.dylib 0x7ff814ea6635 mach_msg_overwrite + 723
    3 libsystem_kernel.dylib 0x7ff814e9f8a8 mach_msg + 19
    4 CoreFoundation 0x7ff814fb9cbe __CFRunLoopServiceMachPort + 145
    5 CoreFoundation 0x7ff814fb872a __CFRunLoopRun + 1360
    6 CoreFoundation 0x7ff814fb7b60 CFRunLoopRunSpecific + 560
    7 AppKit 0x7ff818269179 _NSEventThread + 132
    8 libsystem_pthread.dylib 0x7ff814ede259 _pthread_start + 125
    9 libsystem_pthread.dylib 0x7ff814ed9c7b thread_start + 15

    Thread 0 crashed with X86 Thread State (64-bit):
    rax: 0x000000011c5ebf38 rbx: 0x00007f8343841800 rcx: 0x0000000000000000 rdx: 0x0000000000000000
    rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x00007ff7b13cf1c0 rsp: 0x00007ff7b13cf1a0
    r8: 0x0000000000000055 r9: 0x00000000000000ff r10: 0x0000000000000540 r11: 0x0000600001df1f28
    r12: 0x0000000000000002 r13: 0x00000000000002a0 r14: 0x00007f8342a06f00 r15: 0x0000000000000000
    rip: 0x0000000117481123 rfl: 0x0000000000010246 cr2: 0x0000000001a517c8

    Logical CPU: 5
    Error Code: 0x00000004 (no mapping for user data read)
    Trap Number: 14

    Thread 0 instruction stream:
    05 a4 83 8e 05 00 00 00-00 48 83 c4 10 5b 41 5e ………H…[A^
    5d c3 48 89 c3 48 8d 7d-e8 e8 bf 95 0b 00 48 89 ].H..H.}……H.
    df e8 dd a0 f8 00 0f 0b-0f 1f 44 00 00 55 48 89 ……….D..UH.
    e5 41 89 c8 89 d1 89 f2-89 fe 48 8b 3d f4 1d c3 .A……..H.=…
    05 5d e9 06 00 00 00 66-0f 1f 44 00 00 55 48 89 .]…..f..D..UH.
    e5 41 57 41 56 53 50 49-89 ff 41 83 f8 55 75 07 .AWAVSPI..A..Uu.
    [45]8b 87 c8 17 a5 01 8a-05 c0 84 8e 05 84 c0 75 E…………..u <==
    28 45 39 87 c8 17 a5 01-75 1f 41 39 b7 cc 17 a5 (E9…..u.A9….
    01 75 16 41 39 97 d0 17-a5 01 75 0d 41 39 8f d4 .u.A9…..u.A9..
    17 a5 01 0f 84 07 01 00-00 31 ff 84 c0 40 0f 95 ………1…@..
    c7 45 89 87 c8 17 a5 01-8b 05 3f 83 8e 05 39 f0 .E……..?…9.
    0f 46 f0 83 fe 01 bb 01-00 00 00 0f 46 f3 41 89 .F……….F.A.

    Binary Images:
    0x10eb30000 – 0x11ab7ffff mame (*) /Applications/mame0251-x86/mame
    0x7ff814da6000 – 0x7ff814e2efff libsystem_c.dylib (*) /usr/lib/system/libsystem_c.dylib
    0x7ff814ba5000 – 0x7ff814c39caf dyld (*) /usr/lib/dyld
    0x7ff814ed8000 – 0x7ff814ee3ff7 libsystem_pthread.dylib (*) /usr/lib/system/libsystem_pthread.dylib
    0x7ff814e9e000 – 0x7ff814ed7ff7 libsystem_kernel.dylib (*) /usr/lib/system/libsystem_kernel.dylib
    0x7ff81e635000 – 0x7ff81e65afff (1.0) /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
    0x7ff82ce0f000 – 0x7ff82ce7dff5 (2.0) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
    0x7ff814f3a000 – 0x7ff8153d3fef (6.9) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7ff8180ca000 – 0x7ff8190d2ff2 (6.9) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x0 – 0xffffffffffffffff ??? (*) ???

    External Modification Summary:
    Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
    Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
    Calls made by all processes on this machine:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0

    VM Region Summary:
    ReadOnly portion of Libraries: Total=693.7M resident=0K(0%) swapped_out_or_unallocated=693.7M(100%)
    Writable regions: Total=664.4M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=664.4M(100%)

    REGION TYPE SIZE COUNT (non-coalesced)
    =========== ======= =======
    Accelerate framework 128K 1
    Activity Tracing 256K 1
    CG backing stores 2160K 4
    ColorSync 220K 25
    CoreAnimation 8K 2
    CoreGraphics 12K 2
    CoreServices 108K 1
    Foundation 16K 1
    IOKit 7940K 1
    Image IO 4K 1
    Kernel Alloc Once 8K 1
    MALLOC 376.7M 68
    MALLOC guard page 32K 8
    MALLOC_NANO (reserved) 256.0M 1 reserved VM address space (unallocated)
    STACK GUARD 56.0M 7
    Stack 11.0M 7
    VM_ALLOCATE 184K 21
    __CTF 756 1
    __DATA 56.0M 366
    __DATA_CONST 16.2M 220
    __DATA_DIRTY 739K 118
    __FONT_DATA 2352 1
    __LINKEDIT 235.9M 5
    __OBJC_RO 65.5M 1
    __OBJC_RW 1989K 2
    __TEXT 457.8M 388
    dyld private memory 8448K 3
    mapped file 104.8M 26
    shared memory 792K 20
    =========== ======= =======
    TOTAL 1.6G 1303
    TOTAL, minus reserved VM space 1.4G 1303

    Full Report

    {“app_name”:”mame”,”timestamp”:”2023-02-17 22:37:36.00 +1100″,”app_version”:””,”slice_uuid”:”eb17e24b-c5f5-30fe-88a9-c07f3a513035″,”build_version”:””,”platform”:1,”share_with_app_devs”:0,”is_first_party”:1,”bug_type”:”309″,”os_version”:”macOS 13.2.1 (22D68)”,”roots_installed”:0,”incident_id”:”E679DFB5-9981-439D-BA12-0F694F3AECF8″,”name”:”mame”}
    “uptime” : 160000,
    “procRole” : “Foreground”,
    “version” : 2,
    “userID” : 501,
    “deployVersion” : 210,
    “modelCode” : “MacBookPro16,3”,
    “coalitionID” : 1708,
    “osVersion” : {
    “train” : “macOS 13.2.1”,
    “build” : “22D68”,
    “releaseType” : “User”
    “captureTime” : “2023-02-17 22:37:36.3962 +1100”,
    “incident” : “E679DFB5-9981-439D-BA12-0F694F3AECF8”,
    “pid” : 72336,
    “cpuType” : “X86-64”,
    “roots_installed” : 0,
    “bug_type” : “309”,
    “procLaunch” : “2023-02-17 22:37:00.0769 +1100”,
    “procStartAbsTime” : 162451414514077,
    “procExitAbsTime” : 162487720574430,
    “procName” : “mame”,
    “procPath” : “\/Applications\/mame0251-x86\/mame”,
    “parentProc” : “zsh”,
    “parentPid” : 72314,
    “coalitionName” : “com.googlecode.iterm2”,
    “crashReporterKey” : “93F8781C-2BA7-3EAF-76AB-AB59F1E9E477”,
    “responsiblePid” : 1909,
    “responsibleProc” : “iTerm2”,
    “wakeTime” : 1144,
    “bridgeVersion” : {“build”:”20P3045″,”train”:”7.2″},
    “sleepWakeUUID” : “5CE85C33-6A95-4DD6-BD00-68B1A014B459”,
    “sip” : “enabled”,
    “vmRegionInfo” : “0x1a517c8 is not in any region. Bytes before following region: 4513982520\n REGION TYPE START – END [ VSIZE] PRT\/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n—> \n __TEXT 10eb30000-11ab80000 [192.3M] r-x\/r-x SM=COW …0251-x86\/mame”,
    “exception” : {“codes”:”0x0000000000000001, 0x0000000001a517c8″,”rawCodes”:[1,27596744],”type”:”EXC_BAD_ACCESS”,”signal”:”SIGSEGV”,”subtype”:”KERN_INVALID_ADDRESS at 0x0000000001a517c8″},
    “termination” : {“flags”:0,”code”:11,”namespace”:”SIGNAL”,”indicator”:”Segmentation fault: 11″,”byProc”:”exc handler”,”byPid”:72336},
    “vmregioninfo” : “0x1a517c8 is not in any region. Bytes before following region: 4513982520\n REGION TYPE START – END [ VSIZE] PRT\/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n—> \n __TEXT 10eb30000-11ab80000 [192.3M] r-x\/r-x SM=COW …0251-x86\/mame”,
    “extMods” : {“caller”:{“thread_create”:0,”thread_set_state”:0,”task_for_pid”:0},”system”:{“thread_create”:0,”thread_set_state”:0,”task_for_pid”:0},”targeted”:{“thread_create”:0,”thread_set_state”:0,”task_for_pid”:0},”warnings”:0},
    “faultingThread” : 0,
    “threads” : [{“triggered”:true,”id”:1756128,”instructionState”:{“instructionStream”:{“bytes”:[5,164,131,142,5,0,0,0,0,72,131,196,16,91,65,94,93,195,72,137,195,72,141,125,232,232,191,149,11,0,72,137,223,232,221,160,248,0,15,11,15,31,68,0,0,85,72,137,229,65,137,200,137,209,137,242,137,254,72,139,61,244,29,195,5,93,233,6,0,0,0,102,15,31,68,0,0,85,72,137,229,65,87,65,86,83,80,73,137,255,65,131,248,85,117,7,69,139,135,200,23,165,1,138,5,192,132,142,5,132,192,117,40,69,57,135,200,23,165,1,117,31,65,57,183,204,23,165,1,117,22,65,57,151,208,23,165,1,117,13,65,57,143,212,23,165,1,15,132,7,1,0,0,49,255,132,192,64,15,149,199,69,137,135,200,23,165,1,139,5,63,131,142,5,57,240,15,70,240,131,254,1,187,1,0,0,0,15,70,243,65,137],”offset”:96}},”threadState”:{“r13”:{“value”:672},”rax”:{“value”:4770938680,”symbolLocation”:176,”symbol”:”typeinfo for blit_texrot<unsigned short, unsigned int, op_yuv16pal_argb32rot >”},”rflags”:{“value”:66118},”cpu”:{“value”:5},”r14″:{“value”:140201735253760},”rsi”:{“value”:0},”r8″:{“value”:85},”cr2″:{“value”:27596744},”rdx”:{“value”:0},”r10″:{“value”:1344},”r9″:{“value”:255},”r15″:{“value”:0},”rbx”:{“value”:140201750173696},”trap”:{“value”:14,”description”:”(no mapping for user data read)”},”err”:{“value”:4},”r11″:{“value”:105553147666216},”rip”:{“value”:4685566243,”matchesCrashFrame”:1},”rbp”:{“value”:140701807210944},”rsp”:{“value”:140701807210912},”r12″:{“value”:2},”rcx”:{“value”:0},”flavor”:”x86_THREAD_STATE”,”rdi”:{“value”:0}},”queue”:””,”frames”:[{“imageOffset”:143986979,”imageIndex”:0},{“imageOffset”:131452967,”imageIndex”:0},{“imageOffset”:131453774,”imageIndex”:0},{“imageOffset”:131719340,”imageIndex”:0},{“imageOffset”:131094622,”imageIndex”:0},{“imageOffset”:191519,”symbol”:”__cxa_finalize_ranges”,”symbolLocation”:409,”imageIndex”:1},{“imageOffset”:191033,”symbol”:”exit”,”symbolLocation”:35,”imageIndex”:1},{“imageOffset”:131690928,”imageIndex”:0},{“imageOffset”:25360,”symbol”:”start”,”symbolLocation”:2432,”imageIndex”:2}]},{“id”:1756167,”frames”:[{“imageOffset”:7256,”symbol”:”start_wqthread”,”symbolLocation”:0,”imageIndex”:3}]},{“id”:1756168,”frames”:[{“imageOffset”:7256,”symbol”:”start_wqthread”,”symbolLocation”:0,”imageIndex”:3}]},{“id”:1756187,”frames”:[{“imageOffset”:7256,”symbol”:”start_wqthread”,”symbolLocation”:0,”imageIndex”:3}]},{“id”:1756203,”name”:”caulk.messenger.shared:17″,”frames”:[{“imageOffset”:5438,”symbol”:”semaphore_wait_trap”,”symbolLocation”:10,”imageIndex”:4},{“imageOffset”:116984,”symbol”:”caulk::mach::semaphore::wait_or_error()”,”symbolLocation”:16,”imageIndex”:5},{“imageOffset”:9828,”symbol”:”caulk::concurrent::details::worker_thread::run()”,”symbolLocation”:36,”imageIndex”:5},{“imageOffset”:9000,”symbol”:”void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple > >(void*)”,”symbolLocation”:41,”imageIndex”:5},{“imageOffset”:25177,”symbol”:”_pthread_start”,”symbolLocation”:125,”imageIndex”:3},{“imageOffset”:7291,”symbol”:”thread_start”,”symbolLocation”:15,”imageIndex”:3}]},{“id”:1756272,”frames”:[{“imageOffset”:5570,”symbol”:”mach_msg2_trap”,”symbolLocation”:10,”imageIndex”:4},{“imageOffset”:62980,”symbol”:”mach_msg2_internal”,”symbolLocation”:82,”imageIndex”:4},{“imageOffset”:34357,”symbol”:”mach_msg_overwrite”,”symbolLocation”:723,”imageIndex”:4},{“imageOffset”:6312,”symbol”:”mach_msg”,”symbolLocation”:19,”imageIndex”:4},{“imageOffset”:75264,”symbol”:”XServerMachPort::ReceiveMessage(int&, void*, int&)”,”symbolLocation”:94,”imageIndex”:6},{“imageOffset”:277447,”symbol”:”MIDIProcess::MIDIInPortThread::Run()”,”symbolLocation”:105,”imageIndex”:6},{“imageOffset”:179520,”symbol”:”XThread::RunHelper(void*)”,”symbolLocation”:10,”imageIndex”:6},{“imageOffset”:184243,”symbol”:”CAPThread::Entry(CAPThread*)”,”symbolLocation”:77,”imageIndex”:6},{“imageOffset”:25177,”symbol”:”_pthread_start”,”symbolLocation”:125,”imageIndex”:3},{“imageOffset”:7291,”symbol”:”thread_start”,”symbolLocation”:15,”imageIndex”:3}]},{“id”:1756306,”name”:””,”frames”:[{“imageOffset”:5570,”symbol”:”mach_msg2_trap”,”symbolLocation”:10,”imageIndex”:4},{“imageOffset”:62980,”symbol”:”mach_msg2_internal”,”symbolLocation”:82,”imageIndex”:4},{“imageOffset”:34357,”symbol”:”mach_msg_overwrite”,”symbolLocation”:723,”imageIndex”:4},{“imageOffset”:6312,”symbol”:”mach_msg”,”symbolLocation”:19,”imageIndex”:4},{“imageOffset”:523454,”symbol”:”__CFRunLoopServiceMachPort”,”symbolLocation”:145,”imageIndex”:7},{“imageOffset”:517930,”symbol”:”__CFRunLoopRun”,”symbolLocation”:1360,”imageIndex”:7},{“imageOffset”:514912,”symbol”:”CFRunLoopRunSpecific”,”symbolLocation”:560,”imageIndex”:7},{“imageOffset”:1700217,”symbol”:”_NSEventThread”,”symbolLocation”:132,”imageIndex”:8},{“imageOffset”:25177,”symbol”:”_pthread_start”,”symbolLocation”:125,”imageIndex”:3},{“imageOffset”:7291,”symbol”:”thread_start”,”symbolLocation”:15,”imageIndex”:3}]}],
    “usedImages” : [
    “source” : “P”,
    “arch” : “x86_64”,
    “base” : 4541579264,
    “size” : 201654272,
    “uuid” : “eb17e24b-c5f5-30fe-88a9-c07f3a513035”,
    “path” : “\/Applications\/mame0251-x86\/mame”,
    “name” : “mame”
    “source” : “P”,
    “arch” : “x86_64”,
    “base” : 140703478472704,
    “size” : 561152,
    “uuid” : “1aec5d1a-6e43-30f9-a9f2-11eb85d3e70c”,
    “path” : “\/usr\/lib\/system\/libsystem_c.dylib”,
    “name” : “libsystem_c.dylib”
    “source” : “P”,
    “arch” : “x86_64”,
    “base” : 140703476371456,
    “size” : 609456,
    “uuid” : “bba77709-6cad-3592-ab03-09d0f7b8610e”,
    “path” : “\/usr\/lib\/dyld”,
    “name” : “dyld”
    “source” : “P”,
    “arch” : “x86_64”,
    “base” : 140703479726080,
    “size” : 49144,
    “uuid” : “3bd433d4-15bd-3add-a612-95e4d3b20719”,
    “path” : “\/usr\/lib\/system\/libsystem_pthread.dylib”,
    “name” : “libsystem_pthread.dylib”
    “source” : “P”,
    “arch” : “x86_64”,
    “base” : 140703479488512,
    “size” : 237560,
    “uuid” : “87ff381c-4d30-3087-bab7-a5a53d232c00”,
    “path” : “\/usr\/lib\/system\/libsystem_kernel.dylib”,
    “name” : “libsystem_kernel.dylib”
    “source” : “P”,
    “arch” : “x86_64”,
    “base” : 140703638441984,
    “CFBundleShortVersionString” : “1.0”,
    “CFBundleIdentifier” : “”,
    “size” : 155648,
    “uuid” : “bf7582bd-4de0-3ca2-8b69-f1944725f182”,
    “path” : “\/System\/Library\/PrivateFrameworks\/caulk.framework\/Versions\/A\/caulk”,
    “name” : “caulk”
    “source” : “P”,
    “arch” : “x86_64”,
    “base” : 140703881555968,
    “CFBundleShortVersionString” : “2.0”,
    “CFBundleIdentifier” : “”,
    “size” : 454646,
    “uuid” : “ef0b1eab-34f6-3bee-b85b-792871a8d4cb”,
    “path” : “\/System\/Library\/Frameworks\/CoreMIDI.framework\/Versions\/A\/CoreMIDI”,
    “name” : “CoreMIDI”,
    “CFBundleVersion” : “88”
    “source” : “P”,
    “arch” : “x86_64h”,
    “base” : 140703480127488,
    “CFBundleShortVersionString” : “6.9”,
    “CFBundleIdentifier” : “”,
    “size” : 4825072,
    “uuid” : “c2615780-0140-315c-a455-7e03bb22d3d6”,
    “path” : “\/System\/Library\/Frameworks\/CoreFoundation.framework\/Versions\/A\/CoreFoundation”,
    “name” : “CoreFoundation”,
    “CFBundleVersion” : “1953.300”
    “source” : “P”,
    “arch” : “x86_64”,
    “base” : 140703532097536,
    “CFBundleShortVersionString” : “6.9”,
    “CFBundleIdentifier” : “”,
    “size” : 16814067,
    “uuid” : “540cedfd-5a35-3f35-8953-dcb7c4834eb5”,
    “path” : “\/System\/Library\/Frameworks\/AppKit.framework\/Versions\/C\/AppKit”,
    “name” : “AppKit”,
    “CFBundleVersion” : “2299.40.118”
    “size” : 0,
    “source” : “A”,
    “base” : 0,
    “uuid” : “00000000-0000-0000-0000-000000000000”
    “sharedCache” : {
    “base” : 140703475765248,
    “size” : 21474836480,
    “uuid” : “57815a20-af2c-3b56-9006-23abde7962b0”
    “vmSummary” : “ReadOnly portion of Libraries: Total=693.7M resident=0K(0%) swapped_out_or_unallocated=693.7M(100%)\nWritable regions: Total=664.4M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=664.4M(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 128K 1 \nActivity Tracing 256K 1 \nCG backing stores 2160K 4 \nColorSync 220K 25 \nCoreAnimation 8K 2 \nCoreGraphics 12K 2 \nCoreServices 108K 1 \nFoundation 16K 1 \nIOKit 7940K 1 \nImage IO 4K 1 \nKernel Alloc Once 8K 1 \nMALLOC 376.7M 68 \nMALLOC guard page 32K 8 \nMALLOC_NANO (reserved) 256.0M 1 reserved VM address space (unallocated)\nSTACK GUARD 56.0M 7 \nStack 11.0M 7 \nVM_ALLOCATE 184K 21 \n__CTF 756 1 \n__DATA 56.0M 366 \n__DATA_CONST 16.2M 220 \n__DATA_DIRTY 739K 118 \n__FONT_DATA 2352 1 \n__LINKEDIT 235.9M 5 \n__OBJC_RO 65.5M 1 \n__OBJC_RW 1989K 2 \n__TEXT 457.8M 388 \ndyld private memory 8448K 3 \nmapped file 104.8M 26 \nshared memory 792K 20 \n=========== ======= ======= \nTOTAL 1.6G 1303 \nTOTAL, minus reserved VM space 1.4G 1303 \n”,
    “legacyInfo” : {
    “threadTriggered” : {
    “queue” : “”
    “trialInfo” : {
    “rollouts” : [
    “rolloutId” : “62699e1ec1ff2978b47f6c3b”,
    “factorPackIds” : {
    “SIRI_FIND_MY_CONFIGURATION_FILES” : “631f72d1de559130376df1fb”
    “deploymentId” : 240000023
    “rolloutId” : “60f8ddccefea4203d95cbeef”,
    “factorPackIds” : {

    “deploymentId” : 240000022
    “experiments” : [


    Model: MacBookPro16,3, BootROM 1916. (iBridge: 20.16.3045.0.0,0), 4 processors, Quad-Core Intel Core i5, 1.4 GHz, 16 GB, SMC
    Graphics: Intel Iris Plus Graphics 645, Intel Iris Plus Graphics 645, Built-In
    Display: Color LCD, 2560 x 1600 Retina, Main, MirrorOff, Online
    Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, LPDDR3, 2133 MHz, SK Hynix, H9CCNNNCLGALAR-NVD
    Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, LPDDR3, 2133 MHz, SK Hynix, H9CCNNNCLGALAR-NVD
    AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x870), wl0: Dec 1 2022 22:41:45 version 16.20.356. FWID 01-64eeaab6
    Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
    Network Service: Wi-Fi, AirPort, en0
    USB Device: USB31Bus
    USB Device: T2Bus
    USB Device: Touch Bar Backlight
    USB Device: Touch Bar Display
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: Headset
    USB Device: Ambient Light Sensor
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: Apple T2 Controller
    Thunderbolt Bus: MacBook Pro, Apple Inc., 63.5

    1. The libsystem Library is causing a crash. Basically each MacOS version has its own libsystem version. Older libsystem built software should work on a newer libsystem version system. But newer will never work on a older system. This is Apple’s “version control”, MAME should work on Ventura though, so that’s strange to see. I’ll look into this, I might need to make new builds.

Leave a Reply

Your email address will not be published. Required fields are marked *