Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!pacbell.com!ames!ucsd!hub.ucsb.edu!6600m00n
From: 6600m00n@ucsbuxa.ucsb.edu (Steelworker)
Newsgroups: comp.os.msdos.programmer
Subject: Re: TD 386
Message-ID: <8261@hub.ucsb.edu>
Date: 17 Jan 91 17:38:21 GMT
References: <26342@uflorida.cis.ufl.EDU> <26343@uflorida.cis.ufl.EDU>
Sender: news@hub.ucsb.edu
Reply-To: 6600m00n@ucsbuxa.ucsb.edu
Distribution: usa
Organization: University of California -- Santa Barbara
Lines: 26
In-reply-to: jdb@reef.cis.ufl.edu's message of 16 Jan 91 14:17:39 GMT

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?  Does it use V86 or protected mode?  If it
]  uses protected mode, what happens to all my disk caches (i.e. does protected
]  mode thrash all the XMS that I had allocated for caching, EMS, etc. for 
]  its own use since their were allocated in real modE?)
]
]  Brian

Using td386 allows you to debug large programs.  I use it to debug
a program that takes nearly all main memory, which is impossible using
just td.  Td386 uses V86 mode, similar to how Qemm, 386max, and other
memory managers do.  (note that td386 will not run from a V86
environment of those manegers.)  It requires the driver td386.sys to 
load.   It uses XMS, EMS, or perhaps even extended memory.  

Other advantages are:
	More advanced hardware breakpoints. ( eg break on access to 
a memory location)
	Better trapping of exceptions(?) and better response in general.

Try it out, but it is not needed except for large programs.
Good luck,
Robert Blair
6600m00n@ucsbuxa.ucsb.edu