Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!agate!garnet.berkeley.edu!ked
From: ked@garnet.berkeley.edu (Earl H. Kinmonth)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C Debugger
Message-ID: <11729@agate.BERKELEY.EDU>
Date: 6 Jul 88 23:23:50 GMT
References: <11590@agate.BERKELEY.EDU> <1803@akgua.ATT.COM>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 13

In article <1803@akgua.ATT.COM> brb@akgua.ATT.COM (Brian R. Bainter) writes:
>From article <11590@agate.BERKELEY.EDU>, by ked@garnet.berkeley.edu (Earl H. Kinmonth):
>>>From what I have seen of it, it also
>>>does profiling. Things are getting better and better.
>> 
>> The profiler is pretty dumb compared to that available for **IX
>> systems.
>
>In case you havn't noticed, DOS (unfortunately) is not anywhere
>near **IX. Get real!

There are profilers available for MSDOS that offer a reasonably
close approximation to the profiling available under *IX, for
example the prof program with the MKS Toolkit.  Get educated!