On Tue, 2014-07-22 at 15:20 +0200, Olaf Lenz wrote: > I'm using OpenSUSE 12.3, 64bit. > I have used current valgrind and also the SVN version, but to no > avail. > "nm" tells me that the debuginfo is in the binary, but valgrind won't > find it. > > > I did use valgrind to profile other binaries on the same machine, > built with the same compiler, and it worked fine. Could that be > something in the build system of our software? Or am I safe to say > that when nm finds the info, valgrind should, too? What you could do is to take a binary which is ok, and the binary that is not ok.
Then for both, you run valgrind, increasing the level of tracing/debugging, until you see a difference which could explain what is going wrong with espresso. You could first try with -v and then succesfully add more -v and more -d (up to 3 each). After that, even more heavyweight tracing can be enabled by adding one or more of : --debug-dump=syms --debug-dump=line --debug-dump=frames --trace-symtab=yes Philippe ------------------------------------------------------------------------------ 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
