Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!ucsd!ucbvax!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac
Subject: Re: Path coverage analyzer needed for Mac
Keywords: path coverage
Message-ID: <3139@husc6.harvard.edu>
Date: 6 Jun 90 01:39:36 GMT
References: <11223@pixar.UUCP> <11055@claris.com>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 29

In article <11055@claris.com> rick@claris.com (Rick Boarman) writes:
>
>If you find a good coverage tool please let us all know!! I've checked out
>a few and so far they all are pretty poor.  They require extensive
>modifications to be made to your source.  Some only work for Pascal and
>not for C or C++.  
>
>Why can't someone (Jasik?) create a tool that uses the .SYM and .MAP files
>to monitor the program at interrupt or instruction trace level? It sounds
>so easy...

	It sounds easy, but it is in fact highly nontrivial.
	
	Both THINK Pascal and THINK C come with code profilers; THINK C's
can profile at the function level, and THINK Pascal's can profile at the
statement level. Neither requires any modification of the source, except
for calls to initialize and terminate profiling and to dump the results.

R.
~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"It's not the years, honey, it's the mileage."

~~~~~~~~~~~~~~~