Viewing source functions in kcachegrind when profiling code

[Katie Leonard]

Hello,

I'm trying to use valgrind and kcachegrind to profile my code. However, when I load up the output into kcachegrind, the function calls have unintelligible names like '0x0805fe00' so I can't which bit of my code it refers to.  I would like to have an output as shown in step-22 in the tutorials.

When I press on 'Source Code' within the kcachegrind GUI, I get

"There is no source available for the following function: 

'0x0805fe00'
This is because no debug information is present. 

Recompile source and redo the profile run.
"

However recompiling and rerunning does not solve the problem.  Has anyone else had this problem at all?  

Many thanks,

Katie 

Katie Leonard

DPhil student in Computational Biology,
The University of Oxford.

[Timo Heister]

Hi Katie,

are you using the debug or the release build of deal.II? If you want
to use the optimized build, you need to add -g to the compiler flags.

> --
> The deal.II project is located at http://www.dealii.org/
> For mailing list/forum options, see
> https://groups.google.com/d/forum/dealii?hl=en
>
>



--
Timo Heister
http://www.math.tamu.edu/~heister/

[Wolfgang Bangerth]

> When I press on 'Source Code' within the kcachegrind GUI, I get
>
> "There is no source available for the following function:
> '0x0805fe00'
> This is because no debug information is present.
> Recompile source and redo the profile run.
> "
>
> However recompiling and rerunning does not solve the problem. Has
> anyone else had this problem at all?

Well, do you use debug mode?

Best
W.
--
------------------------------------------------------------------------
Wolfgang Bangerth email: bang...@math.tamu.edu
www: http://www.math.tamu.edu/~bangerth/

[Katie Leonard]

Hi Timo,

Thanks for your email.  It was something to do with the version of the Makefile I was using.  Replacing the makefile 

"# $Id: Makefile 24349 2011-09-21 08:38:41Z kronbichler $" with 

"# $Id: Makefile 24352 2011-09-21 15:12:54Z bangerth $" 

has solved the problem.  So obviously I had an old version on my machine.

Many Thanks,

Katie