 No.13560
Tafoid Administrator
Jan 26, 2017, 21:10
edited on: Jan 26, 2017, 21:20
|
The crash is unintentional. It used to work just fine up until about a year or so ago when some fiddling in debugger seems to have made non-functional cheats (those addressing cpu regions which don't exist, usually) to crash MAME out. The current method to bypass is to use the internal CHEAT plugin instead of -cheat. For some reason, everything works as expected there and it will simply not load the offending cheats. Previous attempts to fix it may not have worked as well as expected - 06241 |
|---|---|
 No.13569
cuavas Administrator
Jan 29, 2017, 22:24
|
It's caused by using exceptions for error propagation when loading cheats, but writing code in a way that's decidedly not exception-safe. The problem is entirely in the cheat code, not the debugger. It's on my TODO list to fix, but it's not my highest priority at the moment. |
|
No.13579
cuavas Administrator
Feb 2, 2017, 07:28
|
On failure to parse an individual cheat, an error message should be printed and the cheat manager should move on to the next cheat. On a problematic cheat file, the cheat manager should print an error message and clear out all cheats. I've also fixed memory leaks, made lots of things const, and generally cleaned up the code. Let me know about any regressions. |
 No.13626
EoceneMiacid Tester
Feb 13, 2017, 19:27
|
Thank you very much Vas! |