08832: All: Unable to enter/activate the debugger for the pacman.cpp driver

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
08832	Debugger	Minor	Always	Mar 6, 2024, 01:09	Mar 6, 2024, 03:19

Tester	chaneman	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Invalid report	OS	Windows 10/11 (64-bit)
Status [?]	Closed			Driver	pacman/pacman.cpp
Version	0.263	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	08832: All: Unable to enter/activate the debugger for the pacman.cpp driver
Description	I mainly use Arcade64 because it is limited to arcade games only, but I always have the official release of MAME in the same folder as Arcade64 along with all the other files needed to run both versions. I am unable to get the Debugger to initialize when running any of the games in the pacman.cpp driver. All other games/drivers loaded will start with the Debugger no problem. I have deleted all the cfg files in the cfg folder as well as the ini file, but this does nothing to bring up the Debugger screen. Not sure if this is a bug or just me.
Steps To Reproduce	Run MAME with the debugger activated for any games in the pacman.cpp driver.
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	All

Attached Files

No.21996 Tafoid Administrator Mar 6, 2024, 02:39	Seems to work just fine in my local testing (pacman, pengo, vanvan tested). Also tested a DEBUG=1 build of 0.263 with the same results. Is it still running the game without initiating the debugger window(s) or is there a crash/exception/assert or other happenings? How are you launching MAME to invoke the debugger? Be verbose. Best I can suggest is to attempt make a new folder with a newly installed MAME and try again.
No.21997 chaneman Tester Mar 6, 2024, 03:19	Thank you Tafoid. " Best I can suggest is to attempt make a new folder with a newly installed MAME and try again." I did this and it works now. Strange it was only the pacman driver that was affected though?!? This Report can be closed.

No.21996

Tafoid

Administrator

Mar 6, 2024, 02:39

Seems to work just fine in my local testing (pacman, pengo, vanvan tested). Also tested a DEBUG=1 build of 0.263 with the same results.

Is it still running the game without initiating the debugger window(s) or is there a crash/exception/assert or other happenings?
How are you launching MAME to invoke the debugger? Be verbose.

Best I can suggest is to attempt make a new folder with a newly installed MAME and try again.

No.21997

chaneman

Tester

Mar 6, 2024, 03:19

Thank you Tafoid. " Best I can suggest is to attempt make a new folder with a newly installed MAME and try again."
I did this and it works now. Strange it was only the pacman driver that was affected though?!?

This Report can be closed.