Bug 5199 - Feature request: function call logging
Summary: Feature request: function call logging
Status: NEW
Alias: None
Product: gcc
Classification: Unclassified
Component: middle-end (show other bugs)
Version: unknown
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on: 11950
Blocks:
  Show dependency tree / graph
 
Reported: 2001-12-26 18:06 UTC by ghudson
Modified: 2005-12-24 19:53 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2005-12-24 19:53:36

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ghudson 2001-12-26 18:06:01 UTC 
(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.

Release:
n/a
Comment 1 Craig Rodrigues 2001-12-26 19:17:28 UTC 
State-Changed-From-To: open->feedback
State-Changed-Why: Did you try looking at the -finstrument-functions flag?
    See:
    http://gcc.gnu.org/onlinedocs/gcc-3.0.2/gcc_3.html#SEC52
Comment 2 Wolfgang Bangerth 2002-12-21 11:01:54 UTC 
State-Changed-From-To: feedback->closed
State-Changed-Why: No feedback
Comment 3 Wolfgang Bangerth 2003-01-03 08:53:44 UTC 
State-Changed-From-To: closed->open
State-Changed-Why: Reopened based on http://gcc.gnu.org/ml/gcc-bugs/2002-12/msg01195.html
    
    See that mail for some more information
Comment 4 Andrew Pinski 2003-05-24 00:59:04 UTC 
confirmed on mainline (20030523).