Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!philmtl!philabs!ccnysci!ciamac
From: ciamac@ccnysci.UUCP (Ciamac Moallemi)
Newsgroups: comp.sources.d
Subject: Re: v08i002: A C execution profiler for MS-DOS
Summary: CodeScope code profiler
Message-ID: <2717@ccnysci.UUCP>
Date: 22 Aug 89 00:37:03 GMT
References: <64297@uunet.UU.NET> <2559@cbnewsc.ATT.COM>
Reply-To: ciamac@ccnysci.UUCP (Ciamac Moallemi)
Organization: City College Of New York
Lines: 26

In article <2559@cbnewsc.ATT.COM> psfales@cbnewsc.ATT.COM (Peter Fales) writes:
}In article <64297@uunet.UU.NET>, allbery@uunet.UU.NET (Brandon S. Allbery - comp.sources.misc) writes:
}> [...so how about a Turbo C version?  ++bsa]
}
}I feel compelled to point out here that the MKS toolkit includes a
}C profiler that works with any compiler that creates MAP files (i.e.
}uses the Microsoft linker), and requires no modifications to the 
}source, makefile, or object file (i.e. you don't have to link in
}a special .obj).  It does include a utility to add an MKS specific
}symbol table to the .EXE file.

I've seen a shareware code profiler called CodeScope.  It also works
with any compiler that generates a decent .map file (includeing msc
and turbo c).  It's registeration fee is $25 (also gets you source
code) and it is available from:
	CodeCrafters
	P.O. Box 1317
	Londonderry, NH 03053-1317

//cm

-- 
Ciamac Moallemi                       | ciamac@sci.ccny.cuny.edu
Dept. of Earth and Planetary Sciences | cmoallem@puscs.poly.edu
City College of New York              | ciamac@ccnysci.BITNET
           ...!{cmcl2,philabs,phri}!ccnysci!ciamac