function tree trace for a.out's ?

[Brandon S. Allbery KB8JRR/AA]

As quoted from <1991Apr19.150727.17125 at ghost.unimi.it> by matteo at ghost.unimi.it (Matteo Gelosa):
+---------------
| pete at ohm.york.ac.uk (-Pete French.) writes:
| >is possible to do this by hand using the output from nm - but I am sure
| 
| 	NM simly maps a function name with is start address, and prints
| 	it out, so how can you obtain a function calling tree?
+---------------

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.

++Brandon
-- 
Me: Brandon S. Allbery			  Ham: KB8JRR/AA on 2m, 220, 440, 1200
Internet: allbery at NCoast.ORG		(QRT on HF until local problems fixed)
America OnLine: KB8JRR // Delphi: ALLBERY   AMPR: kb8jrr.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery          KB8JRR @ WA8BXN.OH