00154: [debug] Problem in debugger and PSX-based games

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
00154	Misc.	Major	Have not tried	Jan 24, 2008, 17:01	Jan 24, 2008, 17:02

Tester	Firewave	View Status	Public	Platform
Assigned To		Resolution	Fixed	OS
Status [?]	Resolved			Driver
Version	0.117	Fixed in Version	0.117u1	Build	Debug
		Fixed in Git Commit		Github Pull Request #

Summary	00154: [debug] Problem in debugger and PSX-based games
Description	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.
Steps To Reproduce
Additional Information
Github Commit

Flags	Debug build specific
Regression Version
Affected Sets / Systems

Attached Files