https://bugs.kde.org/show_bug.cgi?id=420906
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@klomp.org
Status|REPORTED |ASSIGNED
Ever confirmed|0 |1
Assignee|jsew...@acm.org |m...@klomp.org
--- Comment #5 from Mark Wielaard <m...@klomp.org> ---
(In reply to Florian Weimer from comment #4)
> 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.
valgrind is loosing control over the cloned thread, so it is not just an
annoying warning.
The quickest solution/workaround would be to explicitly ENOSYS clone3 (without
warning) so that glibc falls back to clone.
--
You are receiving this mail because:
You are watching all bug changes.
