On Wed, 16 Aug 2006 at 11:56 +0000, mcrosier@... wrote:
> Maybe someone can help me out here... I hoping to profile Valgrind using
> Oprofile. After starting the Oprofile daemon, I run Valgrind specifying
> the Nullgrind tool (basically the JITer part of Valgrind w/o
> instrumentation). Then to build the annotated source code I execute:
> 'opannotate --source /home/mcrosier/valgrind-test-install/bin/valgrind'
> Unfortunately, I get a response saying there is no profile information.
> Specifically, "error: no sample files found: profile specification too
> strict ?" I then ran Valgrind again and checked top to see that the
> program was actually called "none" which is the Nullgrind tool. After
> calling Valgrind, an exec() is called to execute the front-end tool
> (Nullgrind in this instance). So, I then tried specifying the Nullgrind
> 'opannotate --source /home/mcrosier/valgrind-test/none/none-x86-linux'.
> Unfortunately, I get the same error as above. Running 'opreport' shows
> that the program "none" (not "none-x86-linux") has been profiled... I
> guess my question is how do I specify that I want profile information for
> "none-x86-linux" when the profile log has it labeled as "none".
If I remember correctly valgrind is loaded as a shared library of the
"valgrind'ed" process, so if you:
$ valgrind /my/application
you must use:
$ opannotate --source /my/application
restricting profile report to the valgrind shared lib is possible, see