[Coco] dbg.l

[Stephen H. Fischer]

Hi,

I added the text and the source from the magazine article.
(The source OCR is really bad, Sorry)

It describes how the author implemented the full debugging suite including
single stepping.

That PC code would not be useful for the CoCo and was not included in the
article.

http://www.tandycoco.com/forum/viewtopic.php?p=368&sid=f456c2e2608092b526bb75fea4975a53#p368

------------------------------------------------------------------

Is there not a utility to display the contents of a library, like listing
the routines and entry points.

The dig.l listing would probable tell me if it was worth disassembling.

SHF



----- Original Message ----- 
From: "Willard Goosey" <goosey at virgo.sdc.org>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, May 01, 2011 1:59 PM
Subject: Re: [Coco] dbg.l
...
> OK, but I warned you it doesn't have a lot of useful-to-human
> information:
> -------------------------
> /*
> ** definitions for "debug trace"
> */
>
> #define  TROFF       0
> #define  TRON        1
> #define  E_INTERACT  2
> #define  L_INTERACT  4
>
> ------------------------------
>
> Warned you! ;-)
>
> It looks like dbg.l is an expansion of the MW profiler, that can be set
> to be a little more verbose.  Probably call some setup function with
> TRON to make _prof print the name of each function as it's called.  Or
> something.  Not sure what E_INTERACT and L_INTERACT might control.
>
> Willard