Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06879||Debugger||Minor||Always||28 days ago||12 days ago|
|Tester||drencorxeen||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||Resolution||Open||OS||Windows 10 (64-bit)|
|Version||0.194||Fixed in Version||Build||64-bit|
|Summary||06879: coco2, coco2b, coco3: Debugger causing system emulation to not work correctly|
When starting MAME/MESS with the -debug option on the command line the emulation will not boot from NitrOS-9 L1 correctly. The system when it is trying to load the CPU shows it is jumping to RAM locations that it shouldn't be doing.
When you don't use the -debug option the emulation works as expected without any problems.
So far I have tried this with the coco3.cpp and subsets of coco3, coco3h, and coco3p with same effect. So this behavor is also in other systems besides coco12.cpp
|Steps To Reproduce||
From PowerShell or command prompt I type:
.\mame64.exe coco2 -flop1 NOS9_6809_L1_coco2_80d.dsk -debug
From within the emulated system I type:
I also tried building current bleeding edge sources from github and the issue is still there as well.
So far I have only tested in coco12.cpp and coco3.cpp systems.
|Affected Sets / Systems||coco2, coco2b, coco3|
NOS9_6809_L1_coco2_80d_20180216.zip (179,306 bytes) 28 days ago Uploaded by drencorxeen
NitrOS-9 L1 boot disk 3.5" 720K image
|There are no relationsihp linked to this issue.|
28 days ago
edited on: 28 days ago
Confirmed with -debug and image provided above on coco2 machine.
12 days ago
|I have tested this on Ubuntu 16.04LTS 64bit and also doesn't work correctly there.|