If you can provide minimal C-code (not just nm sources) for identifying
binary with such symbol table and printing the text section relative text
symbols from that, I could later try integrating its automatic use to
Hatari.
I don't have a C code for this, I coded this stuff only in assembler back then but it's pretty simple:
http://toshyp.atari.org/en/005005.html -- really only matter of playing with offsets, not much work at all.
I might some day rewrite the debugger GUI
in Qt/C++
That would be cool.
GUI requires more code though, much more than the actual functionality
in the debugger currently, and it's not scriptable so that one could
automate its usage, so it's not so interesting for me...
Think of us, poor users! ;-) I'm not sure how powerful debugger GUI Steem has but I heard only praising about it. Maybe there's even no GUI, only very user friendly commands?
Trace and profiler functionality should IMHO be dead simple to
use and especially former is really useful in debugging (OS calls,
HW register accesses etc).
I must kick myself to look at it one day. As far as I remember, I everytime ended with the frustration about not knowing where's everything. In MON, you start the app, you see immediately its first instruction, nice labels, disassembled text segment with an arrow showing you "here you are!". And memory dump in a next window. In Hatari, I even don't know where to look if I want to stop it on the first instruction ;-)