gprof and arguments to executable

c++ debugging gprof
Thorvaldur picture Thorvaldur · Apr 8, 2009 · Viewed 18k times · Source

when using gprof:

$ gprof options [executable-file [profile-data-files...]] [> outfile]

if you have options to pass to the executable like:

gprof a.out --varfred=32

then gprof assumes that I am passing an invalid option to it, instead of to the program being profiled (a.out).

Any way to get around this?

Answer

unwind picture unwind · Apr 8, 2009

You don't run your executable with gprof, so you only specify it so gprof can load symbols. You run the executable first, on its own just as normal, and it then emits profiling data.

This data is loaded, along with the executable, by gprof later.

This is all explained in the gprof manual, of course.

Related questions

Debugging with command-line parameters in Visual Studio

I'm developing a C++ command-line application in Visual Studio and need to debug it with command-line arguments. At the moment I just run the generated EXE file with the arguments I need (like this program.exe -file.txt) , but this …

Read More
How do you get assembler output from C/C++ source in gcc?

How does one do this? If I want to analyze how something is getting compiled, how would I get the emitted assembly code?

Read More
__FILE__, __LINE__, and __FUNCTION__ usage in C++

Presuming that your C++ compiler supports them, is there any particular reason not to use __FILE__, __LINE__ and __FUNCTION__ for logging and debugging purposes? I'm primarily concerned with giving the user misleading data—for example, reporting the incorrect line number …

Read More