Your message dated Fri, 14 Nov 2014 10:22:15 +0100
with message-id
<CA+7wUsxw=am6ld4jz4f22+1fnh-cr4acaxht7mxsa9nklrf...@mail.gmail.com>
and subject line i386-dbg is now documented
has caused the Debian Bug report #695218,
regarding valgrind: suggest libc6-dbg:i386 with programs compiled with -m32
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
695218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695218
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: valgrind
Version: 1:3.8.1-1
Severity: normal
When I run valgrind on a program compiled with -m32, I get:
valgrind: Fatal error at startup: a function redirection
valgrind: which is mandatory for this platform-tool combination
valgrind: cannot be set up. Details of the redirection are:
valgrind:
valgrind: A must-be-redirected function
valgrind: whose name matches the pattern: strlen
valgrind: in an object with soname matching: ld-linux.so.2
valgrind: was not found whilst processing
valgrind: symbols from the object with soname: ld-linux.so.2
valgrind:
valgrind: Possible fixes: (1, short term): install glibc's debuginfo
valgrind: package on this machine. (2, longer term): ask the packagers
valgrind: for your Linux distribution to please in future ship a non-
valgrind: stripped ld.so (or whatever the dynamic linker .so is called)
valgrind: that exports the above-named function using the standard
valgrind: calling conventions for this platform. The package you need
valgrind: to install for fix (1) is called
valgrind:
valgrind: On Debian, Ubuntu: libc6-dbg
valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo
valgrind:
valgrind: Cannot continue -- exiting now. Sorry.
The suggested fix is to install libc6-dbg, but it is installed
(see System Information below). Perhaps a libc6-i386-dbg package
would be necessary, in which case the suggested fix mentioned
above is wrong and the above message needs to be corrected.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages valgrind depends on:
ii libc6 2.13-37
ii libc6-dbg 2.13-37
Versions of packages valgrind recommends:
ii gdb 7.4.1-3
ii valgrind-dbg 1:3.8.1-1
Versions of packages valgrind suggests:
pn alleyoop <none>
pn kcachegrind <none>
pn valgrind-mpi <none>
pn valkyrie <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 1:3.10.0-2
This is now properly documented in README.Debian.
--- End Message ---
