Version: 3.6.0 (using Devel) OS: Linux Slackware 10.2 make fails using valgrind-3.6.0.tar.bz2 Reproducible: Always Steps to Reproduce: Unpack tar file run ./configure run ./make Actual Results: Please see Additional Information below Here is the tail of the make output display gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -MT memcheck_x86_linux-mc_errors.o -MD -MP -MF .deps/memcheck_x86_linux-mc_errors.Tpo -c -o memcheck_x86_linux-mc_errors.o `test -f 'mc_errors.c' || echo './'`mc_errors.c mv -f .deps/memcheck_x86_linux-mc_errors.Tpo .deps/memcheck_x86_linux-mc_errors.Po ../coregrind/link_tool_exe_linux 0x38000000 gcc -Wno-long-long -o memcheck-x86-linux -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -static -nodefaultlibs -nostartfiles -u _start -m32 memcheck_x86_linux-mc_leakcheck.o memcheck_x86_linux-mc_malloc_wrappers.o memcheck_x86_linux-mc_main.o memcheck_x86_linux-mc_translate.o memcheck_x86_linux-mc_machine.o memcheck_x86_linux-mc_errors.o ../coregrind/libcoregrind-x86-linux.a ../VEX/libvex-x86-linux.a -lgcc ../coregrind/link_tool_exe_linux: line 50: use: command not found ../coregrind/link_tool_exe_linux: line 51: use: command not found ../coregrind/link_tool_exe_linux: line 54: die: command not found ../coregrind/link_tool_exe_linux: line 61: syntax error near unexpected token `$ala' ../coregrind/link_tool_exe_linux: line 61: ` if (length($ala) < 3 || index($ala, "0x") != 0);' make[3]: *** [memcheck-x86-linux] Error 2 make[3]: Leaving directory `/opt/valgrind-3.6.0/memcheck' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/opt/valgrind-3.6.0/memcheck' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/valgrind-3.6.0' make: *** [all] Error 2
(In reply to comment #0) > ../coregrind/link_tool_exe_linux 0x38000000 gcc -Wno-long-long -o > memcheck-x86-linux -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall > -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes > -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -static > -nodefaultlibs -nostartfiles -u _start -m32 memcheck_x86_linux-mc_leakcheck.o > memcheck_x86_linux-mc_malloc_wrappers.o memcheck_x86_linux-mc_main.o > memcheck_x86_linux-mc_translate.o memcheck_x86_linux-mc_machine.o > memcheck_x86_linux-mc_errors.o ../coregrind/libcoregrind-x86-linux.a > ../VEX/libvex-x86-linux.a -lgcc > ../coregrind/link_tool_exe_linux: line 50: use: command not found A few questions: - Has Perl been installed on your system, and if so, which output do you get for ls -l /usr/bin/perl ? - If a Perl binary exists is present in /usr/bin, does removing the space from the first line of coregrind/link_tool_exe_linux ("#! /usr/bin/perl") help ?
Aha! No perl installed. I didn't realize that it was necessary. I will install it and try again as soon as I get a chance. Thank you! On Fri, Feb 11, 2011 at 2:08 AM, Bart Van Assche <bart.vanassche@gmail.com>wrote: > https://bugs.kde.org/show_bug.cgi?id=266045 > > > Bart Van Assche <bart.vanassche@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |bart.vanassche@gmail.com > > > > > --- Comment #1 from Bart Van Assche <bart vanassche gmail com> 2011-02-11 > 08:08:56 --- > (In reply to comment #0) > > ../coregrind/link_tool_exe_linux 0x38000000 gcc -Wno-long-long -o > > memcheck-x86-linux -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall > > -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes > > -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 > -static > > -nodefaultlibs -nostartfiles -u _start -m32 > memcheck_x86_linux-mc_leakcheck.o > > memcheck_x86_linux-mc_malloc_wrappers.o memcheck_x86_linux-mc_main.o > > memcheck_x86_linux-mc_translate.o memcheck_x86_linux-mc_machine.o > > memcheck_x86_linux-mc_errors.o ../coregrind/libcoregrind-x86-linux.a > > ../VEX/libvex-x86-linux.a -lgcc > > ../coregrind/link_tool_exe_linux: line 50: use: command not found > > A few questions: > - Has Perl been installed on your system, and if so, which output do you > get > for ls -l /usr/bin/perl ? > - If a Perl binary exists is present in /usr/bin, does removing the space > from > the first line of coregrind/link_tool_exe_linux ("#! /usr/bin/perl") help ? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > You reported the bug. >
Bart, I installed perl, then was able to install valgrind. However, it reported a memory leak and seg faulted when I executed valgrind ls -l I looked at the FAQ and re-ran it with option --run-libc-freeres=no, and it no longer reported a memory leak but it still seg faulted. Can you offer any suggestions, or should I submit this as a formal bug? I am including excerpts of the program output below. Thank you, Leo == Valgrind output == ==9831== Memcheck, a memory error detector ==9831== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==9831== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info ==9831== Command: ls -l ==9831== total 1748 -rw-rw-r-- 1 julio 1000 2451 2010-10-20 14:19 AUTHORS -rw-rw-r-- 1 julio 1000 17987 2010-10-20 14:19 COPYING ... -rw-rw-r-- 1 julio 1000 9018 2010-10-20 14:19 xfree-4.supp ==9831== ==9831== HEAP SUMMARY: ==9831== in use at exit: 26,413 bytes in 259 blocks ==9831== total heap usage: 286 allocs, 27 frees, 44,340 bytes allocated ==9831== ==9831== LEAK SUMMARY: ==9831== definitely lost: 0 bytes in 0 blocks ==9831== indirectly lost: 0 bytes in 0 blocks ==9831== possibly lost: 0 bytes in 0 blocks ==9831== still reachable: 26,413 bytes in 259 blocks ==9831== suppressed: 0 bytes in 0 blocks ==9831== Rerun with --leak-check=full to see details of leaked memory ==9831== ==9831== For counts of detected and suppressed errors, rerun with: -v ==9831== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 23 from 8) --9831-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --9831-- si_code=80; Faulting address: 0x0; sp: 0x62c9f29c valgrind: m_signals.c:2328 (sync_signalhandler_from_kernel): Assertion 'tid != 0' failed. ==9831== at 0x38026055: report_and_quit (m_libcassert.c:193) sched status: running_tid=1 ... --9831-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --9831-- si_code=80; Faulting address: 0x0; sp: 0x62c9eb88 --9831-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --9831-- si_code=80; Faulting address: 0x0; sp: 0x62c9e648 ... --9831-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --9831-- si_code=80; Faulting address: 0x0; sp: 0x62ba06c8 On Fri, Feb 11, 2011 at 10:52 AM, Leo Weltman <leoweltman@gmail.com> wrote: > Aha! No perl installed. I didn't realize that it was necessary. I will > install it and try again as soon as I get a chance. > > Thank you! > > > On Fri, Feb 11, 2011 at 2:08 AM, Bart Van Assche <bart.vanassche@gmail.com > > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=266045 >> >> >> Bart Van Assche <bart.vanassche@gmail.com> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> CC| |bart.vanassche@gmail.com >> >> >> >> >> --- Comment #1 from Bart Van Assche <bart vanassche gmail com> 2011-02-11 >> 08:08:56 --- >> (In reply to comment #0) >> > ../coregrind/link_tool_exe_linux 0x38000000 gcc -Wno-long-long -o >> > memcheck-x86-linux -m32 -mpreferred-stack-boundary=2 -O2 -g -Wall >> > -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes >> > -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 >> -static >> > -nodefaultlibs -nostartfiles -u _start -m32 >> memcheck_x86_linux-mc_leakcheck.o >> > memcheck_x86_linux-mc_malloc_wrappers.o memcheck_x86_linux-mc_main.o >> > memcheck_x86_linux-mc_translate.o memcheck_x86_linux-mc_machine.o >> > memcheck_x86_linux-mc_errors.o ../coregrind/libcoregrind-x86-linux.a >> > ../VEX/libvex-x86-linux.a -lgcc >> > ../coregrind/link_tool_exe_linux: line 50: use: command not found >> >> A few questions: >> - Has Perl been installed on your system, and if so, which output do you >> get >> for ls -l /usr/bin/perl ? >> - If a Perl binary exists is present in /usr/bin, does removing the space >> from >> the first line of coregrind/link_tool_exe_linux ("#! /usr/bin/perl") help >> ? >> >> -- >> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email >> ------- You are receiving this mail because: ------- >> You are on the CC list for the bug. >> You reported the bug. >> > >
(In reply to comment #3) > Can you offer any suggestions, or should I submit this as a formal bug? I am > including excerpts of the program output below. You have already filed a formal bug report ;-) It looks like something strange goes wrong with the communication of the signal information between the Slackware kernel and Valgrinds kernel interface. Not sure what goes wrong though. By the way, is Slackware 12 important to you, since not too long ago Slackware 13 has been released ?
I wish that I could even work with Slackware 12. My customer is still running Slackware 10 and may upgrade someday ...but I'm not holding my breath :D Thanks. On Sun, Feb 13, 2011 at 7:49 AM, Bart Van Assche <bart.vanassche@gmail.com>wrote: > https://bugs.kde.org/show_bug.cgi?id=266045 > > > Bart Van Assche <bart.vanassche@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEW > Ever Confirmed|0 |1 > > > > > --- Comment #4 from Bart Van Assche <bart vanassche gmail com> 2011-02-13 > 13:49:20 --- > (In reply to comment #3) > > Can you offer any suggestions, or should I submit this as a formal bug? I > am > > including excerpts of the program output below. > > You have already filed a formal bug report ;-) > > It looks like something strange goes wrong with the communication of the > signal > information between the Slackware kernel and Valgrinds kernel interface. > Not > sure what goes wrong though. > > By the way, is Slackware 12 important to you, since not too long ago > Slackware > 13 has been released ? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > You reported the bug. >
Slackware 10.2 was EOLed on 2012-08-01 valgrind 3.6.0 was released on 21 October 2010