https://bugs.kde.org/show_bug.cgi?id=420906
--- Comment #4 from Florian Weimer <fwei...@redhat.com> --- To reproduce, you can use Fedora rawhide (or 34) and install a glibc build on top of it. https://koji.fedoraproject.org/koji/buildinfo?buildID=1782185 or any build later than glibc-2.33.9000-44.fc35 will do. Building glibc from upstream sources will of course work as well. It is simple to enough to reproduce using Python: >>> import threading >>> threading.Thread(None, lambda: print("Thread is running")).start() --3019-- WARNING: unhandled amd64-linux syscall: 435 --3019-- You may be able to write your own handler. --3019-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --3019-- Nevertheless we consider this a bug. Please report --3019-- it at http://valgrind.org/support/bug_reports.html. Thread is running So things just work (as expected), except for the annoying warning. If you build glibc from upstream sources, you can get to a Python prompt with the just-built glibc like this (without installing): git clone --depth 1 https://sourceware.org/git/glibc.git cd glibc mkdir build cd build ../configure --prefix=/usr make -j`nproc` bash testrun.sh --tool=valgrind /usr/bin/python3 A valgrind binary needs to be on PATH for this. -- You are receiving this mail because: You are watching all bug changes.
