| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09464 | Media Support | Major | Always | 2 days ago | 1 day ago |
| Tester | cuavas | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | cuavas | Resolution | Fixed | OS | Windows (x64) |
| Status [?] | Resolved | Driver | |||
| Version | 0.287 | Fixed in Version | 0.288GIT | Build | x64 |
| Fixed in Git Commit | 448f067 | Github Pull Request # | |||
| Summary |
 09464: MAME no longer attempts to "create" sockets when using socket.<address>:<port> syntax with the bitbanger device |
||||
| Description |
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) |
||||
| Steps To Reproduce |
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 |
||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | Regression | ||||
| Regression Version | 0.282 | ||||
| Affected Sets / Systems | |||||
|
Attached Files
|
|||||
 No.24395
cuavas Administrator
2 days ago
|
Regression is here: https://github.com/mamedev/mame/commit/12bfdf939eecce62a875b800b94872bd938fab0e |
|---|---|
|
No.24396
cuavas Administrator
1 day ago
|
448f067501b1cf500a7c2e4ceeafb9a539b389cd gets it back to where it was previously, in that it will open a listening socket after a failure to connect. It also fixes dying with SIGPIPE if data is written before a connection is accepted. |