MAMEWorld Forums - EmuChat - Re: emeralda+debug=crash

> > > Okay about reset. But what about the buggy ... debugger? Try to run the game more
> > > than once with debug enabled to crash mame in no time.
> >
> > Define "more than once". Are you quitting out entirely between runs? Exiting back
> to
> > the internal picker? Using MAMEUI/UME?
>
> Hello!
>
> I have already said it btw I say it more clearly if needed;
>
> 1. I load MAME, or MAMEFX, MAMEPLUS or whatever. The bug is everywhere.
>
> 2. I enable debug mode for game emeralda
>
> 3. I launch the game itself. I press F5, else the game does not run (it is ok). It
> works, ok...
>
> 4. I close the game (not MAME... just the game) - I return to the game index.
> Obviously, something goes wrong but it's not noticed?
>
> 5. I do not disable the debug mode for the game, I just launch it again. I press F5,
> else the game does not run.
>
> 6. After some seconds, MAME dies regularly. I see it dies when it reaches C17A. More
> or less.

Ahh, the heart of the issue. Step by step explanation is always better when explaining complex bugs. Anyway, this appears to be a multisession bug related to that driver (other tested games also crash). Using the debugger or resetting is not needed to reproduce.

Simply type "mame emeralda", pull up TAB menu and pick "Select New Game" loading the same game or another from that driver (namcona1.c). Shortly after start, it will crash. Looks like a reportable bug on MameTesters to me.