[Coco] ZBUG

[Dave Philipsen]

This is just a personal opinion but I played around with the debugger built into EDTASM many years ago when I first acquired the program pak.  I've also played around with a few debuggers over the years.  And I've had some real head-scratchers at times too.  But for me, I always seem to get the problem figured out by writing a little custom debug code into my program.  A lot of times I'll use an assembler conditional or a flag in the program that turns on my debug mode.  I 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.  And usually it's just something simple like the use of the wrong addressing mode or the stack is not restored correctly or something like that.


Dave

> On Jun 4, 2017, at 10:34 PM, John Mark Mobley <johnmarkmelanie at gmail.com> wrote:
> 
> I am using a cross asembler.
> I want to debug my code in XRoar.  I am using Linux.
> 
> I can run edtasm+ from a ROM cartridge, run zbug and load my code from the
> cassette interface into RAM.
> 
> I can run disk-edtasm and just load zbug.  And load my code from the floppy
> interface so that it does not overwrite zbug.  How do I know what address
> is safe?
> 
> Are there other options.
> 
> -John Mark Mobley
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco