| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
 インターフェイス | 重要 (本体) | 解決済み | 修正済み | 2021-05-15 18:49 | 2021-05-16 14:37 |
| テスター | kmg | 担当者 | AJR | ソース | |
| バージョン | 0.231 | 発生バージョン | 0.228 | 修正バージョン | 0.232 |
| 修正コミット | eb5fc0c | プルリク | |||
| フラグ | |||||
| セット | UI | ||||
| セット詳細 | |||||
| 概 要 | ファイルマネージャーがクラッシュする。 | ||||
| 詳 細 | For any system, accessing File Manager, then a currently populated media slot, then accessing file manager from that submenu crashes MAME with various errors (segmentation faults, malloc errors, etc etc). I'm not setup to debug MAME but from playing around a few minutes it seems that this is due to each cfg's <image_directories> contents. When <device instance="foo" directory="" /> has empty string for a directory the problem strikes. The main issue I'm guessing is a missing reasonable default, say the working directory? It also seems from the errors that if the cfg file doesn't exist yet, directory may be null not just a null string. A secondary issue here is the behavior differs between running a software list item from the command line versus picking one in the UI. The latter properly populates directory with a non-empty string, the former seems to always default to "". Of course this may be moot if "" is handled gracefully :) | ||||
| 再現手順 | Picking on nes arbitrarily: 1) erase nes.cfg 2) mame nes smb1 3) Menu -> File Manager -> cartridge (cart) smb1 (cart) -> [file manager] 4) Boom! Alternate step 2 that gives different error at end: 2) mame nes smb1 -> quit MAME (nes.cfg now has directory="") -> mame nes smb1 | ||||
| 追加情報 | |||||
| 添付ファイル | |||||