There was some hint of a stand-alone debugger for tads3 being developed a couple of years ago. I don’t know if it’s still being worked on so I would like to do my own try at this some time (if it doesn’t prove itself too complicated).
I need to get the basics though. How would one actually hook into the vm? I’ve seen the commit for making frobd builds possible and I’ve successfully compiled it but I don’t quite get the communication bit. If I were to do this, would I need to implement an interface somewhere inside the source code for frobtads or does the t3vm create a server host like in the way the Java vm does (that can be connected to via a port) or is some socket communication expected with the external debugger?
if possible it would be great if someone had a rough TODO list of what’s actually is needed to communicate back and forth with the vm, using what protocol etc. Figuring out implementing the actual methods in the debugger I think I can manage since there’s lot of general information on this already out there already.
Anything at all that could get me started would be greatly appreciated.