[ オリジナルレポート ]

BugID: #09464

カテゴリ 重要度 ステータス 解決状況 登録日時 最終更新
解決済み修正済み2026-05-26 03:41昨日 04:03
 
テスターcuavas担当者cuavasソース
バージョン0.287発生バージョン0.282修正バージョン0.288GIT
修正コミット 448f067プルリク
フラグ再発
セット
セット詳細
 
概 要ソケットの生成シンタックスが動作しない。
詳 細Previously, MAME would attempt to open an existing file, then attempt to create a file. It now only attempts to open an existing file. This means it will only create a connecting socket, not a listening socket. It affects Linux as well as Windows, although the error number is different since it’s implementation-defined (generic:107 on Windows, generic:111 on Linux).


Relevant verbose output from MAME 0.281 (working):

:tty:null_modem:stream: attempting to load media image socket.127.0.0.1:1234
:tty:null_modem:stream: error opening image file socket.127.0.0.1:1234 with flags=00000003 (generic:107 Unknown error)
Unable to load image 'socket.127.0.0.1:1234': Unknown error (generic:107)
:tty:null_modem:stream: attempting to create media image socket.127.0.0.1:1234
:tty:null_modem:stream: opened image file socket.127.0.0.1:1234 with flags=00000007
Starting INTELLEC 4/MOD 40 ':'


Relevant verbose output from MAME 0.282 (regressed):

:tty:null_modem:stream: attempting to load media image socket.127.0.0.1:1234
:tty:null_modem:stream: error opening image file socket.127.0.0.1:1234 with flags=00000003 (generic:107 Unknown error)
Unable to load image 'socket.127.0.0.1:1234': Unknown error (generic:107)
Fatal error: Device Bitbanger load (-bitbanger socket.127.0.0.1:1234) failed: Unknown error (generic:107)
再現手順Start a system specifying a valid local TCP enpoint that no process is listening on as media, e.g. I used:
mame intlc440 -tty null_modem -bitb socket.127.0.0.1:1234 -v
追加情報 
 
添付ファイル