https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #9 from Christoph Cullmann <cullm...@kde.org> --- I tried now my 6.1 Qt application again. There with 3.16.1 I still get (even if self compiled): valgrind: m_syswrap/syswrap-main.c:1957 (vgPlain_client_syscall): Assertion '0 == (sci->flags & ~(SfMayBlock | SfPostOnFail | SfPollAfter))' failed. host stacktrace: ==301193== at 0x58041B2A: show_sched_status_wrk (m_libcassert.c:406) ==301193== by 0x58041C47: report_and_quit (m_libcassert.c:477) ==301193== by 0x58041DD7: vgPlain_assert_fail (m_libcassert.c:543) ==301193== by 0x5809AB4F: vgPlain_client_syscall (syswrap-main.c:1980) ==301193== by 0x5809617A: handle_syscall (scheduler.c:1208) ==301193== by 0x58098177: vgPlain_scheduler (scheduler.c:1526) ==301193== by 0x580E38D0: thread_wrapper (syswrap-linux.c:101) ==301193== by 0x580E38D0: run_a_thread_NORETURN (syswrap-linux.c:154) sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 56 (lwpid 301193) ==301193== at 0x83E9A9D: syscall (in /usr/lib/libc-2.33.so) ==301193== by 0x7E5EF86: forkfd (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==301193== by 0x7E461D1: QProcessPrivate::startProcess() (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==301193== by 0x7E40E09: QProcessPrivate::start(QFlags<QIODeviceBase::OpenModeFlag>) (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==301193== by 0x15E5E09: main (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/a3c) client stack range: [0x1FFEFE9000 0x1FFF000FFF] client SP: 0x1FFEFFE058 valgrind stack range: [0x10034B8000 0x10035B7FFF] top usage: 8328 of 1048576 And I still get it with 3.17, too, for the Qt 6.x version. valgrind: m_syswrap/syswrap-main.c:1957 (vgPlain_client_syscall): Assertion '0 == (sci->flags & ~(SfMayBlock | SfPostOnFail | SfPollAfter))' failed. host stacktrace: ==304423== at 0x58041F1A: show_sched_status_wrk (m_libcassert.c:406) ==304423== by 0x58042037: report_and_quit (m_libcassert.c:477) ==304423== by 0x580421C7: vgPlain_assert_fail (m_libcassert.c:543) ==304423== by 0x5809C76F: vgPlain_client_syscall (syswrap-main.c:1980) ==304423== by 0x58097D1A: handle_syscall (scheduler.c:1208) ==304423== by 0x58099D17: vgPlain_scheduler (scheduler.c:1526) ==304423== by 0x580E8110: thread_wrapper (syswrap-linux.c:101) ==304423== by 0x580E8110: run_a_thread_NORETURN (syswrap-linux.c:154) sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 56 (lwpid 304423) ==304423== at 0x83EEA9D: syscall (in /usr/lib/libc-2.33.so) ==304423== by 0x7E63F86: forkfd (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==304423== by 0x7E4B1D1: QProcessPrivate::startProcess() (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==304423== by 0x7E45E09: QProcessPrivate::start(QFlags<QIODeviceBase::OpenModeFlag>) (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==304423== by 0x15E5E09: main (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/a3c) client stack range: [0x1FFEFE9000 0x1FFF000FFF] client SP: 0x1FFEFFDFC8 valgrind stack range: [0x10034B8000 0x10035B7FFF] top usage: 8688 of 1048576 The KWrite test with Qt 5.15.2 does trigger for 3.16.1 this less obvious output: --314055-- WARNING: unhandled amd64-linux syscall: 439 --314055-- You may be able to write your own handler. --314055-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --314055-- Nevertheless we consider this a bug. Please report --314055-- it at http://valgrind.org/support/bug_reports.html. -- You are receiving this mail because: You are watching all bug changes.
