I tried to do a valgrind --tool=memcheck (version 2.4.0 of valgrind) on our "spaceInvaders" clone (a QT multi-threaded application using Opengl and FMOD). As soon as I execute this line, I get a crash and a line mentionning a bug in vg_transtab.c (read on for the output)... I'm using Fedora Core 3, with all official updates.. I compiled valgrind from the source that I got from the web site. Something that's worth mentionning is that I got a segfault in the make process... I just repeated the "make" command, and it did not complain again... After that I did a make install (it installed in /usr/lib/valgrind , I specified "--prefix=/usr" in the ./configure). Here's the output of uname -a : Linux gbr-linux 2.6.10-1.770_FC3 #1 Thu Feb 24 14:00:06 EST 2005 i686 i686 i386 GNU/Linux The output of valgrind --tool=memcheck --leak-check=yes -v ./spaceInvaders : ==23798== Memcheck, a memory error detector for x86-linux. ==23798== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al. ==23798== Using valgrind-2.4.0, a program supervision framework for x86-linux. ==23798== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al. ==23798== Valgrind library directory: /usr/lib/valgrind ==23798== Command line ==23798== ./spaceInvaders ==23798== Startup, with flags: ==23798== --tool=memcheck ==23798== --leak-check=yes ==23798== -v ==23798== Contents of /proc/version: ==23798== Linux version 2.6.10-1.770_FC3 (bhcompile@porky.build.redhat.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Thu Feb 24 14:00:06 EST 2005 ==23798== Reading syms from /home/yop83/log2000-29/inf2700/spaceInvaders (0x8048000) ==23798== Reading syms from /lib/ld-2.3.5.so (0x1B8E4000) ==23798== object doesn't have any debug info ==23798== Reading syms from /usr/lib/valgrind/stage2 (0xB0000000) ==23798== Reading syms from /lib/ld-2.3.5.so (0xB1000000) ==23798== object doesn't have any debug info ==23798== Reading syms from /usr/lib/valgrind/vgskin_memcheck.so (0xB7BE6000) ==23798== Reading syms from /lib/tls/libc-2.3.5.so (0xB7E47000) ==23798== object doesn't have any debug info ==23798== Reading syms from /lib/libdl-2.3.5.so (0xB7F71000) ==23798== object doesn't have any debug info ==23798== Reading suppressions file: /usr/lib/valgrind/default.supp ==23798== valgrind: vg_transtab.c:594 (vgPlain_add_to_trans_tab): Assertion `i == 0 || off > prev' failed. ==23798== at 0xB00372AF: vgPlain_skin_assert_fail (vg_mylibc.c:1170) ==23798== by 0xB00372AE: assert_fail (vg_mylibc.c:1166) ==23798== by 0xB0037309: vgPlain_core_assert_fail (vg_mylibc.c:1177) ==23798== by 0xB007A896: vgPlain_add_to_trans_tab (vg_transtab.c:594) ==23798== by 0xB0079CCC: vgPlain_translate (vg_translate.c:2577) ==23798== by 0xB0019D45: handle_tt_miss (vg_scheduler.c:626) ==23798== by 0xB001A0FE: vgPlain_scheduler (vg_scheduler.c:742) ==23798== by 0xB0087D1A: vgArch_thread_wrapper (core_os.c:69) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==23798== at 0x1B8E47C0: (within /lib/ld-2.3.5.so) ***I cut out the explanatory text about the faq and the bug report**** Also, the output of ls -l /lib/libc*, if it helps (sorry the dates are in french): (avr = april; fév = february; aoû = august; mar = march) -rwxr-xr-x 1 root root 1505808 avr 7 06:58 /lib/libc-2.3.5.so lrwxrwxrwx 1 root root 11 fév 28 17:17 /lib/libcap.so -> libcap.so.1 lrwxrwxrwx 1 root root 14 fév 28 16:57 /lib/libcap.so.1 -> libcap.so.1.10 -rwxr-xr-x 1 root root 11788 aoû 31 2004 /lib/libcap.so.1.10 -rwxr-xr-x 1 root root 192456 avr 7 06:58 /lib/libcidn-2.3.5.so lrwxrwxrwx 1 root root 16 avr 8 16:11 /lib/libcidn.so.1 -> libcidn-2.3.5.so lrwxrwxrwx 1 root root 17 avr 6 22:09 /lib/libcom_err.so.2 -> libcom_err.so.2.1 -rwxr-xr-x 1 root root 7004 mar 8 08:00 /lib/libcom_err.so.2.1 -rwxr-xr-x 1 root root 28552 avr 7 06:58 /lib/libcrypt-2.3.5.so -rwxr-xr-x 1 root root 933408 oct 5 2004 /lib/libcrypto.so.0.9.7a lrwxrwxrwx 1 root root 19 fév 28 16:58 /lib/libcrypto.so.4 -> libcrypto.so.0.9.7a lrwxrwxrwx 1 root root 17 avr 8 16:11 /lib/libcrypt.so.1 -> libcrypt-2.3.5.so lrwxrwxrwx 1 root root 13 avr 8 16:11 /lib/libc.so.6 -> libc-2.3.5.so My hardware: Pentium 3 733 Mhz 512 Mb of ram Nvidia Geforce FX 5200 128 Mb of Ram Sound blaster Live! Value
So it happens instantly, but only with this program? Does it do it with other opengl programs? Are you using the nvidia driver? What does ldd say?
hi! Thanks for your comment, I never tought about testing it with other things... I tested it with glxgears and it gives the same error (and yes, I'm using the Nvidia driver, version 1.0.7167). Just to be sure, I tested it with ls and with nano (command line tools not opengl related), and always the same error!! (about ldd, if you meant what version I have it's : 2.3.5. If it's something else you want to know, just tell me...) It seems that whatever I try, it gives out the same message! Then, it sounds as if my installion would be at fault, right ?
The code that was failing here is completely different in the 3.0.x releases so could you try one of those and let us know whether you still have a problem.
I'm closing crashing and similar bugs that are more than two years old. If you still see this problem with Valgrind 3.4.1 please reopen the bug report. Thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!