help-gsasl
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GNU SASL 1.9.2 and valgrind


From: Bruno Haible
Subject: GNU SASL 1.9.2 and valgrind
Date: Sat, 26 Dec 2020 19:24:00 +0100
User-agent: KMail/5.1.3 (Linux/4.4.0-197-generic; KDE/5.18.0; x86_64; ; )

On Ubuntu 16.04 x86_64, in 32-bit mode (CC="gcc -m32"), configure, make,
and "make install" work fine, but "make -k check" fails several tests:

FAIL: test-error

FAIL: external
FAIL: cram-md5
FAIL: digest-md5
FAIL: md5file
FAIL: name
FAIL: errors
FAIL: suggest
FAIL: simple
FAIL: crypto
FAIL: scram
FAIL: scramplus
FAIL: symbols
FAIL: readnz
FAIL: gssapi
FAIL: gs2-krb5
FAIL: saml20
FAIL: openid20
FAIL: scram-sha256
FAIL: scram-simple
FAIL: scram-nopasswd
FAIL: startcb
FAIL: old-simple
FAIL: old-md5file
FAIL: old-cram-md5
FAIL: old-digest-md5
FAIL: old-base64

The log of each of the failed tests has this:

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 reason is that the /usr/bin/valgrind programs apparently works fine
with 64-bit programs but not with 32-bit programs.

Bruno




reply via email to

[Prev in Thread] Current Thread [Next in Thread]