| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
 その他 | 中 | 解決済み | 修正済み | 2008-01-25 02:01 | 2008-01-25 02:02 |
| テスター | Firewave | 担当者 | ソース | ||
| バージョン | 0.117 | 発生バージョン | 修正バージョン | 0.117u1 | |
| 修正コミット | プルリク | ||||
| フラグ | デバッグビルド限定 | 旧BugID | debbuger+psx_0117ora | ||
| セット | |||||
| セット詳細 | |||||
| 概 要 | デバッガとプレステベースゲームの問題。 | ||||
| 詳 細 | It's a problem I had with MESS and MAME in the past, but I totally forgot about it. It's mainly with PSX-based games. Start "tekken" with the debugger enabled and "-str 2". Then run it with "go" and it will run for a while and suddenly stop without any message or obvious (at least for me) reason. You have to run "go" at least one more time to finally reach the exitpoint. All other games before that (in the -listxml order) ran the amount specified and exited without a problem. I expereicned some other games, that didn't properly "go", but those were unfinished and also reported in most cases "user-initiated breakpoint". This also happens with crusnwld. | ||||
| 再現手順 | |||||
| 追加情報 | |||||
| 添付ファイル | |||||