🚀 go-pugleaf

In article <1991Jan19.015022.20618@bronze.ucs.indiana.edu> rschmidt@copper.ucs.indiana.edu (roy schmidt) writes:
>In article <26343@uflorida.cis.ufl.EDU> jdb@reef.cis.ufl.edu (Brian K. W. Hook) writes:
>>
>>I am pondering using Turbo Debugger in the 386 mode.  Does anyone know the
>>advantages of running this way?
>
>For advantages, read pp. 250-251 of the TD manual, or any other Borland
>hype on their product. :-)

One of the big advantages is being able to use some of the 386's hardware
debugging support, such as break on (read/write/any) memory access, for a
specific location or range of locations. TD in normal mode can do a check
for memory changed, but 1) it only detects changes and worse, 2) it's done
in software so it's miserably slow. Using the hardware support, it runs at
essentially full speed.

One of the things that I haven't seen mentioned much is that YOU DON'T HAVE
TO BE RUNNING TD386 TO GET THIS! If you have the driver (tdh386.sys)
installed, TD running in normal mode can access the hardware debugging
stuff. I tried it for a lark one day, and lo and behold, it worked. This is
TD 2.0 on an ordinary Compaq 386/20e. Furthermore, it coexists peacefully 
with NFS, which TD386 does not.

-- 
James W. Birdsall   WORK: jwbirdsa@amc.com   {uunet,uw-coco}!amc-gw!jwbirdsa
HOME: {uunet,uw-coco}!amc-gw!picarefy!jwbirdsa OTHER: 71261.1731@compuserve.com
"The OS shouldn't die every time the controller drools on a sector." -- a sysop
=========== "For it is the doom of men that they forget." -- Merlin ===========