(Sometimes I can get the information I want by stepping through a program with gdb. But that can be tedious when you don't have a good starting point other than main(), and tricky when a program makes heavy use of threads and/or subprocesses. Function call logging would let me get all of the call trace information into one place where I could sort through it in a variety of ways.)
Thanks for your consideration.
State-Changed-Why: Did you try looking at the -finstrument-functions flag?
State-Changed-Why: No feedback
State-Changed-Why: Reopened based on http://gcc.gnu.org/ml/gcc-bugs/2002-12/msg01195.html
See that mail for some more information
confirmed on mainline (20030523).