OProfile allows samples for shared libraries to be
attributed to individual executables with the
"--separate-samples". For a program that spends a
majority of its time in the shared libraries, e.g.
mozilla, there may be samples for the shared libraries,
but not be any samples for the main executable. The
file search logic for oprofpp fails when there are
samples for the shared library, but no samples for the
main executable. When this occurs something like the
following error message is printed.
failed. No such file or directory
Better behavior would be for oprofpp to assume there
are zero samples on the executable and not give an
error. For some events it would be possible that they
were never observed during the execution of the
program, e.g. use of mmx or floating point instructions.