[hatari-devel] Symbol name/address support added to Hatari debugger

Eero Tamminen eerot at users.berlios.de
Sun Jan 17 22:25:36 CET 2010


Hi,

On Thursday 14 January 2010, Eero Tamminen wrote:
> > > Laurent, would you be interested about similar support for DSP? :-)
> >
> > Yes I would if it doesn't annoy you ;)
>
> I think I'll first complete the symbols support for CPU and then move
> to DSP breakpoint support.

DSP "dspaddress" breakpoints have now also symbols support.  You can
use the "dspsymbols" command to load the DSP symbol names & addresses[1].
After that "dspaddress" TAB completion can complete the loaded symbols.

[1] For the format, see tests/etos512.sym for an example.  "T" means that
     the address is for TEXT section i.e. code.  (I've thought that I could 
     later add support for symbols also to conditional breakpoints, then
     one can set also breakpoints on data & bss section changes (data
     changes) using their symbolic names in code.)


Btw. Other things that I've added to the symbol support:
1) Whenever you break to breakpoint at some symbol address, it shows
   the symbol name too.  Symbol names are also shown when listing or
   deleting breakpoints.  This is for both CPU & DSP.
2) When disassembling memory from the debugger, it shows the symbols,
   like this:
----------
00e01032: 60e4 2f0a 45f9 0000 530e BT .B #$ffffffe4 == 00e01018 (TRUE)
_random:
00e01034: 2f0a 45f9 0000 530e 4a92 MOVE.L A2,-(A7)
00e01036: 45f9 0000 530e 4a92 6614 LEA.L $0000530e,A2
00e0103c: 4a92 6614 2039 0000 04ba TST.L (A2)
----------

DSP disassembly doesn't show the symbolic address names because code
for that does the whole range and that code is not in the debugdsp.c.

For the same reason (it not being done in debugger code) the symbol names
are not show when using CPU disassembly tracing.


> Btw. Did the things listed in "Hatari debugger improvements" thread have
> anything you would specifically like to see supported for DSP
> breakpoints?

After I've finished the improved GEMDOS emu long host names support, I had
thought to look into counted CPU & DSP address breakpoints.   But if you
have any comments on things you would think useful from that list, please
comment! :-)


	- Eero



More information about the hatari-devel mailing list