| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 05210 | Crash/Freeze | Critical (emulator) | Always | May 31, 2013, 23:44 | Apr 7, 2014, 11:02 |
| Tester | Tafoid | View Status | Public | Platform | |
| Assigned To | wilbert | Resolution | Fixed | OS | |
| Status [?] | Resolved | Driver | |||
| Version | 0.148u5 | Fixed in Version | 0.153 | Build | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 05210: kram3: Black Screen/Hangs Emulator on startujp | ||||
| Description | Application must be killed or if you run with -watchdog trigger, the emulation will hait that way. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | 0.148u2 | ||||
| Affected Sets / Systems | kram3 | ||||
|
Attached Files
|
 start.png (22,403 bytes) Jun 4, 2013, 09:00 Uploaded by Robbbert | ||||
| next.png (22,021 bytes) Jun 4, 2013, 09:01 Uploaded by Robbbert Code has turned into garbage after 2 steps
| |||||
 No.09578
NekoEd Senior Tester
Jun 2, 2013, 03:37
|
Confirmed on SDLMAME64/Linux 0.148u5 That's a nasty one, you actually have to SIGKILL it, it hangs bad enough that SIGTERM doesn't work. |
|---|---|
 No.09579
hap Developer
Jun 3, 2013, 19:15
|
Even though the kram3 set is broken for now. IMO, under no circumstances should any rom be able to lock up MAME. |
|
No.09580
NekoEd Senior Tester
Jun 4, 2013, 02:56
|
No red or yellow warnings on kram3. But you're right, even if it's got every red flag in the book it should never jam up the works like that. |
 No.09581
Robbbert Senior Tester
Jun 4, 2013, 09:04
|
Note the 2 snaps above from the debugger. The first is when the game starts, the second is after 2 steps, you can see the disassembly has changed. The program gets to A793 where it loops forever. But if I type g, then it requires task manager to kill it. |
|
No.10175
hap Developer
Jan 12, 2014, 20:25
|
I'm pretty sure the problem is in emu/video/mc6845.c, it needs to be made safer, being able to cope with every possible set of parameters. The cause of lockup is not in m6809.c |
|
No.10176
NekoEd Senior Tester
Jan 13, 2014, 01:00
|
Removed additional information fingering the 6809 core per Osso's observations. |
 No.10178
Osso Moderator
Jan 13, 2014, 07:08
|
They were hap's observations, but since I have been summoned ;) : the source code states "The kram3 set used to be playable with the implementation in the MAME M6809 CPU core, encrypting only the first byte in 10 xx and 11 xx opcodes. This should be moved to the driver file. Until then, kram3 is broken on purpose." So maybe the source code notes needs updating too? |
|
No.10180
NekoEd Senior Tester
Jan 14, 2014, 18:06
|
Oops, sorry Osso. But at least we got some good insight. Leaving as Open/Confirmed since it still locks up MAME hard, intentionally broken or not. ;3 |
|
No.10188
wilbert Developer
Jan 17, 2014, 21:22
|
Fixed in revision 27139 |