https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #2 from Jack Zhao <jack.zhao.f...@gmail.com> --- Hi, thanks for the response. For what it's worth, I was able to reproduce this with a barebones centos7 container. Please see log here: https://pastebin.com/raw/VbvL0khy Steps I took: 1. run a container of the centos:7 official image available from docker.io sudo docker run -i -t centos:7 /bin/bash 2. once in container, install gcc, gcc-c++, and valgrind yum install -y gcc gcc-c++ valgrind 3. download the attached repro case from some available server (or use any method to get the repro case into the container) curl http://<some_server>/test_repro.tar.gz 4. unpack the repro case tar xvzf test_repro.tar.gz 5. cd into the test_repro folder cd test_repro 6. run repro.sh ./repro.sh The test_repro.tar.gz will be attached right after. So if it's an environment-induced problem, it seems to happen in default/typical environments. Any guidance on what kind of environment settings might be causing it? Thanks! -- You are receiving this mail because: You are watching all bug changes.
