https://bugs.kde.org/show_bug.cgi?id=395266
--- Comment #5 from Paul Floyd <pjfl...@wanadoo.fr> --- There are two possible places that this could be going wrong. 1. The valgrind launcher. This modifies the environment to insert a couple of variables so that Valgrind will be able to load a couple of shared libraries. 2. The tool code that sets up the client env. This synthesizes a new env for the client, adding a LD_PRELOAD. To eliminate number 1 could you try something like this: export VALGRIND_LAUNCHER=`which valgrind` export VALGRIND_LIB=/usr/libexec/valgrind env 'FOO/BAR=1' /usr/libexec/valgrind/memcheck-amd64-linux ./395266 (note that this is NOT a recommended way to run Valgrind!) -- You are receiving this mail because: You are watching all bug changes.
