Nicola Bernardini wrote:

>  Concerning
> a code analyser, being an old unix fart the best I can think of is a
> nice
> run which 'ctrace'. There are two problems: 1) we should do many runs
> with
> very different orcs and scores to really understand some statistic
> path
> of the code; 2) to the best of my knowledge, there is no public domain
>
> 'ctrace' (if somebody knows of such an item please let me know - I am
> *very* interested).

What are code analysers and ctrace?

--
Gabriel Maldonado

http://www.agora.stm.it/G.Maldonado/home2.htm

On Sun, 22 Feb 1998, Gabriel Maldonado wrote:

[snip]
> 
> What are code analysers and ctrace?

a code analyzer is exactly what its name says: it is some piece of software
which shows (at my time that used to be with a printout, could well
be graphically by now...) what the code is doing while running.

Ctrace was(is?) a really neat package that exists on AT&T unix
development platforms which picks up C source code and insert statements
to print out variables as each program statement is executed, so
that when the resulting code gets executed it lets you follow the
execution statement by statement and the global control flow. This,
combined with the cxref software (which print a cross-reference of
all symbols used in a program, along with the location where they are
used), constituted a very helpful software development support.

Unfortunately, both applications are, to the best of my knowledge,
AT&T code and there are no replacements in the public domain (linux
has something call strace which traces operating system calls as
a program goes along, but that's hardly the same thing). So much
for these...

Nicola
------------------------------------------------------------------------
Nicola Bernardini
E-mail: nicb@axnet.it
 
Re graphics: A picture is worth 10K words -- but only those to describe
the picture.  Hardly any sets of 10K words can be adequately described
with pictures.