Am 22.07.2014 14:31, schrieb Olaf Lenz:
> Hi Josef!
> 
> I have just installed valgrind-3.9.0, and it doesn't solve the problem. 
> Also, the problem seems to be there in memcheck, so it seems to be a
> problem with the debuginfo loader.
> Is there a way to explicitly check the loader?

Hmm. You could check the current SVN version. There are some fixes
for the DWARF loader. Also, a sync with the demangler code from
gdb was recently done.
Or recompile (part of the code) with different debug info generation
flags of the compiler (-gdwarf-3, -gstabs, ..).
What compiler/architecture is this?

Josef


> 
> Olaf
> 
> 
> 2014-07-22 10:25 GMT+02:00 Josef Weidendorfer <josef.weidendor...@gmx.de
> <mailto:josef.weidendor...@gmx.de>>:
> 
>     Hi Olaf,
> 
>     Am 21.07.2014 14 <tel:21.07.2014%2014>:48, schrieb Olaf Lenz:
>     > Hi everybody!
>     >
>     > I am trying to use callgrind (3.8.0) to profile our simulation software
>     > ESPResSo (http://espressomd.org) on Linux.
>     >
>     > Unfortunately, callgrind seems to loose the information on where to find
>     > the source files when running the binary.  When I use 'nm -lC Espresso'
>     > on the binary file, I see that the binary does contain the source code
>     > information, e.g.:
> 
>     Can you check out with Valgrind 3.9.0 ?
>     This is not Callgrind related, but about the debuginfo loader, which
>     also
>     should affect the other tools, such as memcheck output on finding
>     errors.
>     It would be good if you can confirm that.
> 
>     If the problem persists, please open a bug.
> 
>     Josef
> 
>     >
>     > 000000000049e605 W add_lj_pair_force(Particle*, Particle*,
>     > IA_parameters*, double*, double, double*)
>     >  /home/olenz/projects/espresso/src/src/core/lj.hpp:45
>     >
>     > However, when I run the binary under callgrind, the output file does not
>     > contain any of the symbols from the binary file, but only the addresses.
>     >
>     > Interestingly, when I test callgrind on a simple test program,
>     > everything works fine...
>     >
>     > Steps to reproduce:
>     > 1. Download source code.
>     > 2. Compile with
>     >> configure CXXFLAGS="-O0 -g"
>     >> make
>     > 3. Check the binary file that it contains symbols:
>     >> nm -lC Espresso | grep add_lj_pair_force
>     > 4. Run test with
>     >> cd testsuite
>     >> valgrind --tool=callgrind ../Espresso lj.tcl
>     > 5. Examine "callgrind.out.XXX": no symbols are contained.
>     >
>     > Does anybody have an idea what goes wrong?
>     >
>     > Olaf
>     >
>     > --
>     > Dr. rer. nat. Olaf Lenz
>     > Institut für Computerphysik, Allmandring 3, D-70569 Stuttgart
>     > Phone: +49-711-685-63607
>     >
>     >
>     > 
> ------------------------------------------------------------------------------
>     > Want fast and easy access to all the code in your enterprise? Index and
>     > search up to 200,000 lines of code with a free copy of Black Duck
>     > Code Sight - the same software that powers the world's largest code
>     > search on Ohloh, the Black Duck Open Hub! Try it now.
>     > http://p.sf.net/sfu/bds
>     >
>     >
>     >
>     > _______________________________________________
>     > Valgrind-users mailing list
>     > Valgrind-users@lists.sourceforge.net
>     <mailto:Valgrind-users@lists.sourceforge.net>
>     > https://lists.sourceforge.net/lists/listinfo/valgrind-users
>     >
> 
>     
> ------------------------------------------------------------------------------
>     Want fast and easy access to all the code in your enterprise? Index and
>     search up to 200,000 lines of code with a free copy of Black Duck
>     Code Sight - the same software that powers the world's largest code
>     search on Ohloh, the Black Duck Open Hub! Try it now.
>     http://p.sf.net/sfu/bds
>     _______________________________________________
>     Valgrind-users mailing list
>     Valgrind-users@lists.sourceforge.net
>     <mailto:Valgrind-users@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/valgrind-users
> 
> 
> 
> 
> -- 
> Dr. rer. nat. Olaf Lenz
> Institut für Computerphysik, Allmandring 3, D-70569 Stuttgart
> Phone: +49-711-685-63607

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to