Path: utzoo!mnetor!uunet!husc6!sri-unix!ctnews!pyramid!hplabs!hpda!hpcuhb!hpindda!hardin
From: hardin@hpindda.HP.COM (John Hardin)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C source level debugger
Message-ID: <4330037@hpindda.HP.COM>
Date: 7 Mar 88 21:27:32 GMT
References: <337@ttrde.UUCP>
Organization: HP Information Networks, Cupertino, CA
Lines: 23

>/ hpindda:comp.sys.ibm.pc / wtm@neoucom.UUCP (Bill Mayhew) 
>
>There was a prototype Turbo C debugger that made an appearance on
>Compuserve about 6 months ago.  It was in a pretty primitive state,
>but it could read the map files, thus providing the ability to
>single step through the program, etc.  I don't know if it is still
>there; I think you go to the Borland SIG.  (I'm not a compuserve
>regular.)  It was not freely redistributable, so you have to get it
>from them.
>----------

The debugger on Compuserve is called TCDEBUG.  I believe it's in a
file called TCDEBU.ARC in data library 4 on the BPROGB forum.  The
latest version of which I am aware is .07 and was uploaded sometime
in January adding the ability to display singly subscripted arrays
in the variable monitoring window.  It's a pretty nice debugger which 
lets you see your source code while debugging, create a window for
monitoring variables, and show the assembly code generated by the 
source whenever you want.  The biggest thing missing is easy access
to local variables.

John
----------