https://bugs.kde.org/show_bug.cgi?id=395266
Paul Floyd changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=395266
--- Comment #8 from Timo Sirainen ---
Yes, original problem exists in Ubuntu 20.04.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395266
--- Comment #7 from Paul Floyd ---
Do you have the original problem with Ubuntu as well?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395266
--- Comment #6 from Timo Sirainen ---
(In reply to Paul Floyd from comment #5)
> 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/l
https://bugs.kde.org/show_bug.cgi?id=395266
--- Comment #5 from Paul Floyd ---
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.
https://bugs.kde.org/show_bug.cgi?id=395266
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #4 from Mark Wielaar
https://bugs.kde.org/show_bug.cgi?id=395266
--- Comment #3 from Paul Floyd ---
An optimization (LTO?) problem perhaps. Ill leave this open - can you please
update if the Debian folks have more info?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395266
--- Comment #2 from Timo Sirainen ---
Looks like there's something weird in the Debian packaging. If I get the
sources with "apt source valgrind" and then compile it with:
./configure --prefix=/tmp/valgrind && make && sudo make install
Then it works c
https://bugs.kde.org/show_bug.cgi?id=395266
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
