detecting function calls

[IAMTubby]

Hey,
Is there a way to know what functions were called by a program during it's execution ?

Say, I have a code, as follows

#include <stdio.h>

int main(void)
{
 fun1();
 fun2();
 fun3();

 return 0;
}

int fun1(){}
int fun2(){fun2_1();}
int fun3(){}

int fun2_1(){}

Here, the output should be something like

Functions called are as follows
fun1()
fun2()
fun2_1()
fun3()


Is there an option on gcc for this ?

[raja.genupula]

Hey,
Is there a way to know what functions were called by a program during it's execution ?

Say, I have a code, as follows

#include <stdio.h>

int main(void)
{
 fun1();
 fun2();
 fun3();

 return 0;
}


int fun1(){}
int fun2(){fun2_1();}
int fun3(){}

int fun2_1(){}

Here, the output should be something like

Functions called are as follows
fun1()
fun2()
fun2_1()
fun3()


Is there an option on gcc for this ?

simple one , how about placing a printf line ?

[IAMTubby]

simple one , how about placing a printf line ?

Hey raja,
hmm.. not too sure if I want to do that, I want to write something which would automatically tell me what functions are called.
Placing a printf is manual right ?

[trent.josephsen]

I don't know of any "automatic" method. Calling a function doesn't leave a trace on the call stack after you return, so you'd have to insert some code at the beginning of every function. The simplest way to do this would be just to stick an extra line in the C source.

gdb might be able to do something like this; it still wouldn't be fully "automatic" though.

Perhaps you should describe what problem you're trying to solve, rather than how you want to solve it, and we can suggest other solutions.

[raja.genupula]

this is for statements , how about using it for your function call

http://stackoverflow.com/questions/8...s-is-executing

[dwhitney67]

You can run your C or C++ program through a profiler.

Look into gprof. You will also need to compile your applications using the -pg option.

[spjackson]

You can use profiling to tell you how often functions were called, average length of execution etc. There is also a tool to do static analysis that will give you a tree of what calls what. But neither of these seem to be what you want, i.e. an automatic call trace at runtime that prints a trace whenever a function is called.

ltrace and strace do tracing, but not at this level. I'm not aware of a standard tool that does just what you want, but there may be one.

Someone's had a go here, but it seems that it hasn't been updated for a while.

This gives some strong clues, but it is 7 years old, and I don't know if it would actually work.

[IAMTubby]

this is for statements , how about using it for your function call

http://stackoverflow.com/questions/8...s-is-executing

raja.genupla, I shall read up on pstack and get back to you. I need 1 day to try out some of the things mentioned on your link. Shall try out and get back surely.

[IAMTubby]

You can run your C or C++ program through a profiler.

Look into gprof. You will also need to compile your applications using the -pg option.

dwhitney, yes Sir, thanks a lot.
I tried running a sample program using gprof, was very helpful .
But I need 1 day to think about it.
I shall try out and get back to you tomorrow.

Thanks.

[IAMTubby]

You can use profiling to tell you how often functions were called, average length of execution etc.

Thanks spjackson, but what is the name of the profiling tool ? gprof ? I just tried a sample program using that and liked it. Any other profiling tool?

There is also a tool to do static analysis that will give you a tree of what calls what.

Sir, would you be able to tell me the name of the tool ?

But neither of these seem to be what you want, i.e. an automatic call trace at runtime that prints a trace whenever a function is called.

At runtime, would have been great, but static is also manageable.

ltrace and strace do tracing, but not at this level. I'm not aware of a standard tool that does just what you want, but there may be one.

Sir, I shall try them and get back to you in 1 day's time. Currently, held up with some other personal commitment.

Someone's had a go here, but it seems that it hasn't been updated for a while.

This gives some strong clues, but it is 7 years old, and I don't know if it would actually work.

I shall refer the links and get back.

Thanks