Bug 20824 – Valgrind internal error when run

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description jsado_sc3 2003-05-11 20:48:39 UTC]

I've got valgrind 1.9.3, and when I run it on my program like this:
valgrind ./color_test
I get this error:

VG_(mash_LD_PRELOAD_and_LD_LIBRARY_PATH): internal error:
   what                = 3
   ld_preload_str      =
`/usr/lib/valgrind/vgskin_memcheck.so:/usr/lib/valgrind/valgrind.so:'
   ld_library_path_str = `/usr//qt/3/lib:/usr//qt/3/lib:/usr//qt/3/lib:'
   p_prel              = `valgrind.so:'
   p_path              = `(null)'
   VG_LIBDIR           = `/usr/lib'

Note that this is often caused by mis-installation of valgrind.
Correct installation procedure is:
   ./configure --prefix=/install/dir
   make install
And then use /install/dir/bin/valgrind
Moving the installation directory elsewhere after 'make install'
will cause the above error.  Hand-editing the paths in the shell
scripts is also likely to cause problems.


valgrind: the `impossible' happened:
   VG_(mash_LD_PRELOAD_and_LD_LIBRARY_PATH) failed

Basic block ctr is approximately 1400000

sched status:

Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==21720==    at 0x402E4411: __execve (in /lib/libc-2.2.5.so)
==21720==    by 0x80654EA: shell_execve (in /bin/bash)

Since it mentions that this is probably caused by a misinstallation, I am filing
this bug.

Reproducible: Always
Steps to Reproduce:




Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2, glibc-2.2.5-r7)
=================================================================
System uname: 2.4.20 i586 AMD-K6(tm) 3D processor
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config /etc/inet.d/net.eth0
/etc/make.profile/packages
/usr/X11R6/lib/X11/xkb:/usr/kde/3/share/config:/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss 3dnow avi crypt encode gif jpeg kde gnome libg++ mikmod motif mpeg
ncurses pdflib png spell truetype xml2 xmms zlib gdbm berkdb slang readline arts
svga tcltk java guile X sdl gpm libwww ssl python esd imlib oggvorbis gtk qt
opengl -mmx -apm pda bonobo evo gtkhtml lcms -tcpd tetex perl -cups -nls -pam
-quicktime -xv gtk2 mozilla 3dfx voodoo3 dga"
COMPILER="gcc3"
CHOST="i586-pc-linux-gnu"
CFLAGS="-Os -fomit-frame-pointer -march=i586"
CXXFLAGS="-Os -fomit-frame-pointer -march=i586"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"

[Comment 1 Robin Johnson 2003-05-11 21:49:13 UTC]

could you please try to re-emerge valgrind?

[Comment 2 jsado_sc3 2003-05-12 18:02:13 UTC]

I just ran emerge valgrind, but there is no change in behavior.

[Comment 3 solar (RETIRED) 2003-08-09 08:40:06 UTC]

There is a new version of valgrind in the portage tree (valgrind-2.0_pre20030725)
Please test and report back any probems if this bug still exists.

[Comment 4 jsado_sc3 2003-08-11 16:55:33 UTC]

The latest version of Valgrind does not exhibit this error. Unfortunately calltree is not up-to-date for use with this version of Valgrind, and Kcachegrind depends on this old version of calltree.

[Comment 5 solar (RETIRED) 2003-08-25 11:31:53 UTC]

Well that's definitely a catch-22.
Is there any type of resolution you would like to see on this if so please share.

[Comment 6 jsado_sc3 2003-08-26 17:47:53 UTC]

It's not really a catch-22. The current latest version of kcachegrind and calltree work with the latest version of valgrind. I would like to see an ebuild for each of these, with the correct dependencies.

I've built the latest packages by hand (resolving dependencies with ebuilds where I could) and it works fine.

[Comment 7 solar (RETIRED) 2003-09-04 21:34:48 UTC]

please open a bug to get kcachegrind and calltree updated.

[Comment 8 solar (RETIRED) 2003-09-05 07:53:15 UTC]

Cant do anything more with valgrind itself. Dont forget to open a bug for the others.