On 07/28/2011 01:17 AM, Ranjan Maitra wrote: > I have been trying to use valgrind with Fedora 15 and I find that I am > not getting the complete backtrace information. Let me provide a simple > example: Valgrind works fine for me: ==6073== Conditional jump or move depends on uninitialised value(s) ==6073== at 0x3CE8C497BB: vfprintf (in /lib64/libc-2.14.so) ==6073== by 0x3CE8C4B0C3: buffered_vfprintf (in /lib64/libc-2.14.so) ==6073== by 0x3CE8C467ED: vfprintf (in /lib64/libc-2.14.so) ==6073== by 0x3CE8C50B76: fprintf (in /lib64/libc-2.14.so) ==6073== by 0x40052A: main (test.c:5) > Compile with: > > gcc -o -g test test.c This won't generally run successfully - you're asking gcc to compile "test" and "test.c" and put the output in a file named "-g". Depending on what "test" is this will most likely fail in different (weird!) ways. You probably want something like: gcc -o test -g test.c Is it possible you had an old version of "test" lying around and it lacks debug symbols? Regards, Bryn. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
