> I'm trying to use valgrind to debug my program, but I can't seem to get any > line numbers to display in the output... [snip] > I've tried compiling with "g++ -O0 -g" ... [snip] > Any suggestions?
Compile and link the smallest executable which gives a problem. Apply "gzip -9", then attach both the source code and the binary executable program to a bug report; see http://valgrind.org/support/bug_reports.html . Remember to identify the system and versions. For example: ----- $ uname -a Linux f14-64.local 2.6.35.14-106.fc14.x86_64 #1 SMP Wed Nov 23 13:07:52 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ g++ --version g++ (GCC) 4.5.1 20100924 (Red Hat 4.5.1-4) $ rpm -q glibc libstdc++ glibc-2.13-2.x86_64 libstdc++-4.5.1-4.fc14.x86_64 $ cat hello.cpp #include <iostream> main() { std::cout << "Hello, world.\n"; } $ g++ -g hello.cpp $ gzip -9 a.out $ ls -l a.out.gz -rwxrwxr-x. 1 myself user 7240 Nov 30 07:53 a.out.gz $ ----- -- ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
