function tree trace for a.out's ?

[Jim Balter]

In article <1991Apr20.171557.19792 at NCoast.ORG> allbery at ncoast.ORG (Brandon S. Allbery KB8JRR/AA) writes:
>If (and only if) you adhere to a one-function-per-source-file scheme, you can
>do this by treating "U" lines as refs and others as defs.  If you have
>multiple functions per file, you lose:  you can't localize it by function,
>only by file.

Nope.  Executables don't contain unresolved references ('"U" lines').
And in .o's, the unresolved references are bracketed by the function
definitions and thus the call structure is determinable, and cflow does it.
Number of functions per file is irrelevant.