[Coco] ZBUG

[Dave Philipsen]

Well, I suppose that would work.  I'm personally not into the emulators.  I've done a lot of work on embedded systems and usually it is custom hardware without a specific dev system set up for it.  I assemble the code on a PC, upload to the target in RAM, run it and debug.  Once you have it debugged burn the program to EPROM, flash, or whatever.

Even with CoCo3FPGA there is hardware present that is, I assume, not present in the emulator.  Easiest way in my book is just the old-fashioned way.  I've never used the debugger under OS9 even when I wrote a fairly complicated terminal program back in the 80s. Always debugged using my own code.  Never had a debugger on any of the custom embedded systems I've worked on either. Personal preference I suppose or maybe I'm just to set in my ways to change.



Dave

> On Jun 5, 2017, at 11:44 PM, Mark McDougall <msmcdoug at iinet.net.au> wrote:
> 
>> On 6/06/2017 2:34 PM, Dave Philipsen wrote:
>> 
>> may write a little subroutine that, when called, does a dump of all
>> of the registers and displays their contents or something like that.
>> It always seems  to be easier than trying to run a debugger.
> 
> Specifying '-debug' on the command line and then hitting the <`> key or any breakpoint in the MAME debugger will show the current register values. Doesn't get any easier than that IMHO!?!
> 
> Regards,
> 
> -- 
> Mark McDougall
> <http://retroports.blogspot.com.au>
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco