pete-gordon
Suggested new Debugger CPU and disassembly layout
A:00 00000000
X:00 00000000
Y:00 00000000
VIA NV0BDIZC
PC:EB88 SP:F8
NMI:$0247 >EB88 60 __ __ RTS
RST:$F88F
IRQ:$0244
CY:005411328
FM:000271
RS:000
Now what would be really cool (but some extra work) would be to extend the
disassembly before the current execution row.
I'm not asking you to work out what it should be (by looking at the bytes)
but rather it should echo the known disassembly. For example if the rows
before have been disassemnbled before or the current execution line has
passed the lines before then display above execution line.
It might be better to highlight the execution line differently, such as in
Yellow or bright blue/Cyan background with black font.
Since related directly to the CPU i have illustrated putting the current
hard vectors of FFFA to FFFF here aswell. I think it makes sense and would
be useful.
Also in your original layout you display the Program Status register
purely in binary. It looks much nicer if each bit is directly represented
by the letter designated to it and hyphen or space shown where it is not
set.
Finally i think it makes alot of sense to display the binary aswell as the
hexadecimal value held in the registers although not really enough space
to display $ and % signs.
Using Oricutron 0.5 under windows build.
Original issue reported on code.google.com by [email protected] on 29 Mar 2010 at 10:52
Well, i've added the reset/nmi/irq vectors.
Original comment by [email protected] on 6 Feb 2012 at 5:24
@pete-gordon: This is not directly related to the original issue, but I will look at the debugger code to see if it's possible (without breaking the existing one) to have a windowed version of the debugger, aka a version that use a different window for debugging. The idea is to be able to use the native OS UI for debugging, and even have the ability to keep the Oric running while having the debugger opened. I will be a long road for that, but I think that the improvement would be great
