https://bugs.kde.org/show_bug.cgi?id=483711
--- Comment #7 from John Reiser ---
Current state with fixed the shell script, re-configure, and re-build:
export CC=$HOME/bin/my_gcc_32_or_64
export CXX=$HOME/bin/my_g++_32_or_64
./configure --prefix=$HOME/local
= my_gcc_32_or_64
#! /bin/bash
#
https://bugs.kde.org/show_bug.cgi?id=483711
John Reiser changed:
What|Removed |Added
CC||jrei...@bitwagon.com
--- Comment #6 from John Rei
https://bugs.kde.org/show_bug.cgi?id=483711
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #5 from Mark Wielaar
https://bugs.kde.org/show_bug.cgi?id=483711
--- Comment #4 from Paul Floyd ---
Can you provide an exe that reproduces the problem?
As far as I know none of the Valgrind developers use Docker, and x86 isn't
actively supported, so there's not much chance of this being fixed.
It might help if you
https://bugs.kde.org/show_bug.cgi?id=483711
--- Comment #3 from railway_bylaws...@icloud.com ---
(In reply to railway_bylaws.0b from comment #2)
> Of course, I have just repeated the same steps with ver 3.22.0, but
> unfortunately the outcome remains the same, albeit a bit more detailed.
>
>
> =
https://bugs.kde.org/show_bug.cgi?id=483711
--- Comment #2 from railway_bylaws...@icloud.com ---
Of course, I have just repeated the same steps with ver 3.22.0, but
unfortunately the outcome remains the same, albeit a bit more detailed.
==10121== Command: ./test
==10121==
valgrind: m_scheduler/
https://bugs.kde.org/show_bug.cgi?id=483711
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=483711
railway_bylaws...@icloud.com changed:
What|Removed |Added
Summary|-m32 flag "impossible" |-m32 flag breaks Valgrind
