🚀 go-pugleaf

    We have a fairly large application program for which we would like
    to automatically generate a dynamic routine calling tree (actually,
    several such traces are necessary, as these change with problem type).

    I hacked together a little shell script that use 'bind' to get a
    list of all procedures, generates DEBUG break commands, then runs
    the program under the debugger.  Works most of the time (debugger
    even seems to accept 500+ breakpoints), though I have had trouble
    with infinite looping somewhere on one particular program.  And it
    sure is ugly.

    Is there a better way?

If I understand what you want, there sure is:  There is an Apollo product
called DPAK.  This product is a set of tools and documentation, the most
interesting tool being "dpat".  "dpat" is a Dialog-based (i.e. point
and click) tool that dynamically monitors a program's call stack,
collecting sample tracebacks, optionally displaying them dynamically
(with some performance hit, of course) and, after the program stops, lets
you analyze the samples in a variety of ways.  It's quite sophisticated
(i.e. a far cry from "hpc").

            -- Nat Mishkin
               Apollo Computer Inc.

-------