General Category > LisaList2
LisaEm Debugger
rayarachelian:
--- Quote from: D.Finni on July 31, 2020, 01:42:04 pm ---Could you open a pipe to the GNU assembler (or whichever binary is available) and pass it a couple lines, then get back its output?
--- End quote ---
Meh, I'd rather not, I'd rather compile it in. I think Generator has a lot of the stuff needed for an assembler built in, at least the decode side is there, so I'd need to write some code to recognize the various address modes and what opcode is used and then form the binary. Not as easy as that since there's a lot to do, but it would be doable eventually. I'd need to invert some of the tables it has or build an opcode tree that's searchable and returns patterns and masks, or something like that.
I looked over gas and a68 and they're more complex than I'm looking for sadly. Of the three, yeah, EASy68k is the simplest after all.
I think for a first pass, I'd skip the assembler bit.
So priority right now is:
1. "The opcode bug(s)"
2. reverting the 32 bit mode code + adapting the opcodes that need them - if it turns out that it doesn't need the high byte in the A regs, I may skip this altogether depending on whether fixing 1 is sufficient.
3. next RC release
4. blu+xprofile support+tools
5. pty support for the z8530
6. access to the host serial ports from z8530 (possibly pty is sufficient to launch cu or minicom, so maybe 3 isn't needed)
7. some other features I'd rather not disclose yet as i'm unsure about due to timing and feasibility.
8. rewriting the documentation
9. cleanup + prod release 1.2.7
10. debugger for 1.2.8
11 any other left over features that didn't make it in 1.2.7 before resurrecting the 1.3.0 cpu core and backporting all the fixes to it for 2.0
rayarachelian:
So back to the debugger, I think I want to have a memory display pane with 4-5 buttons above it for contexts 0-4 (0=SIO space), and the last one for physical untranslated memory. I might either add the disassembler to the side of that as a separate frame, or perhaps as 6th button for the same window.
Then at the bottom would be a frame with the registers and some more info about the emulator, then below that another frame where you can type in commands.
I need to figure out how to make the memory window clickable/editable. Need something to find the size of the font and where the click is, etc.
Would this work for you? Is there any specific command or feature you'd like?
D.Finni:
--- Quote from: rayarachelian on July 31, 2020, 03:33:24 pm ---Is there any specific command or feature you'd like?
--- End quote ---
Yeah, that sounds good. I think that a memory dump with hex and ASCII would be good enough for now. I think it's better to get the absolute basics coded first, then start adding the fancy features next.
Just think: if you spent 4 months building a symbolic debugger that could parse heap zones, etc., you could probably reverse engineer and document the Lisa OS in the next 1 month.
stepleton:
It's taking me about that long to do just the 2K of expansion card boot ROM on the AppleNet card :'( ;)
rayarachelian:
--- Quote from: stepleton on July 31, 2020, 06:56:25 pm ---It's taking me about that long to do just the 2K of expansion card boot ROM on the AppleNet card :'( ;)
--- End quote ---
Hint hint: I hear very good things about https://ghidra-sre.org/ - it does support the 68000.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version