|
emeralda+debug=crash
#298632 - 11/07/12 08:16 PM
|
|
|
Hello; I am running the rom called EMERALDA.ZIP
It seems to work fine normally.
I enable the debugger. It works fine again.
Then, if I make it run a second time, after some seconds MAME crashes completely. Same thing happens on MAMEUI and other frontends.
Any idea? 
uh - also, the soft reset is not working... I hit F3 and the game goes stuck
Cheers - Luca
Edited by darkbeam (11/07/12 08:18 PM)
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: emeralda+debug=crash
[Re: darkbeam]
#298642 - 11/07/12 09:45 PM
|
|
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3137
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: emeralda+debug=crash
[Re: darkbeam]
#298644 - 11/07/12 10:11 PM
|
|
|
> Hello; I am running the rom called EMERALDA.ZIP
>
> It seems to work fine normally.
>
> I enable the debugger. It works fine again.
> Then, if I make it run a second time, after some seconds MAME crashes completely.
> Same thing happens on MAMEUI and other frontends.
>
> Any idea?
>
> uh - also, the soft reset is not working... I hit F3 and the game goes stuck
>
> Cheers - Luca
Soft Reset (F3) is not an automatic thing and in my opinion should not exist. Many games it works fine, other.. not so fine. It largely depends on emulation state and even if the board itself had a 'reset' button in the first place. Everyone should use (SHIFT-F3) for a Hard Reset (akin to shutting it off, then back on) to ensure that all data is started in the right order and everything is reset properly.
|
|
|
|
Re: emeralda+debug=crash
[Re: Tafoid]
#298661 - 11/08/12 11:02 AM
|
|
|
> > Hello; I am running the rom called EMERALDA.ZIP
> >
> > It seems to work fine normally.
> >
> > I enable the debugger. It works fine again.
> > Then, if I make it run a second time, after some seconds MAME crashes completely.
> > Same thing happens on MAMEUI and other frontends.
> >
> > Any idea?
> >
> > uh - also, the soft reset is not working... I hit F3 and the game goes stuck
> >
> > Cheers - Luca
>
> Soft Reset (F3) is not an automatic thing and in my opinion should not exist. Many
> games it works fine, other.. not so fine. It largely depends on emulation state and
> even if the board itself had a 'reset' button in the first place. Everyone should use
> (SHIFT-F3) for a Hard Reset (akin to shutting it off, then back on) to ensure that
> all data is started in the right order and everything is reset properly.
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. 
|
|
|
|
Re: emeralda+debug=crash
[Re: B2K24]
#298662 - 11/08/12 11:03 AM
|
|
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: emeralda+debug=crash
[Re: darkbeam]
#298667 - 11/08/12 05:31 PM
|
|
|
> 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?
|
|
|
|
Re: emeralda+debug=crash
[Re: R. Belmont]
#298669 - 11/08/12 06:33 PM
|
|
|
> > 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.
|
|
|
| Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3137
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: emeralda+debug=crash
[Re: darkbeam]
#298671 - 11/08/12 07:41 PM
|
|
|
> > > 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.
|
|
|
|
Re: emeralda+debug=crash
[Re: Tafoid]
#298673 - 11/08/12 08:38 PM
|
|
|
Oh, okay - Do I need to report it? Or is it already reported?
|
|
|
Index 
Threaded 
emeralda+debug=crash
Reply
[Re: 
I press F5, else the game does not run (it is ok). It works, ok...
I see it dies when it reaches C17A. More or less.
