https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #4 from Christoph Cullmann <cullm...@kde.org> --- Ok, just tried it, system is up-to-date Manjaro. I downloaded now https://sourceware.org/pub/valgrind/valgrind-3.17.0.tar.bz2 and do like you told below ;) I think 3.17 fixes the issue for me, at least, my new "simple" test case: 1) open default kwrite of Manjaro 2) open file dialog is now fine, before I got: valgrind: m_syswrap/syswrap-main.c:1957 (vgPlain_client_syscall): Assertion '0 == (sci->flags & ~(SfMayBlock | SfPostOnFail | SfPollAfter))' failed. host stacktrace: ==3711011== at 0x58041B2A: show_sched_status_wrk (m_libcassert.c:406) ==3711011== by 0x58041C47: report_and_quit (m_libcassert.c:477) ==3711011== by 0x58041DD7: vgPlain_assert_fail (m_libcassert.c:543) ==3711011== by 0x5809AB4F: vgPlain_client_syscall (syswrap-main.c:1980) ==3711011== by 0x5809617A: handle_syscall (scheduler.c:1208) ==3711011== by 0x58098177: vgPlain_scheduler (scheduler.c:1526) ==3711011== by 0x580E38D0: thread_wrapper (syswrap-linux.c:101) ==3711011== by 0x580E38D0: run_a_thread_NORETURN (syswrap-linux.c:154) sched status: running_tid=1 Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. ==3711014== Warning: invalid file descriptor 4354 in syscall clone() valgrind: m_syswrap/syswrap-main.c:1957 (vgPlain_client_syscall): Assertion '0 == (sci->flags & ~(SfMayBlock | SfPostOnFail | SfPollAfter))' failed. host stacktrace: ==3711014== at 0x58041B2A: show_sched_status_wrk (m_libcassert.c:406) ==3711014== by 0x58041C47: report_and_quit (m_libcassert.c:477) ==3711014== by 0x58041DD7: vgPlain_assert_fail (m_libcassert.c:543) ==3711014== by 0x5809AB4F: vgPlain_client_syscall (syswrap-main.c:1980) ==3711014== by 0x5809617A: handle_syscall (scheduler.c:1208) ==3711014== by 0x58098177: vgPlain_scheduler (scheduler.c:1526) ==3711014== by 0x580E38D0: thread_wrapper (syswrap-linux.c:101) ==3711014== by 0x580E38D0: run_a_thread_NORETURN (syswrap-linux.c:154) sched status: running_tid=1 now I see no such errors! I only get: ==3711230== Syscall param waitid(infop) points to unaddressable byte(s) ==3711230== at 0x65FAA9D: syscall (in /usr/lib/libc-2.33.so) ==3711230== by 0x60172D7: ??? (in /usr/lib/libQt5Core.so.5.15.2) ==3711230== by 0x5FFB2DB: ??? (in /usr/lib/libQt5Core.so.5.15.2) ==3711230== by 0x6E9C4BB: ??? (in /usr/lib/libKF5KIOCore.so.5.80.0) ==3711230== by 0x6E9C698: ??? (in /usr/lib/libKF5KIOCore.so.5.80.0) ==3711230== by 0x6E9CE49: ??? (in /usr/lib/libKF5KIOCore.so.5.80.0) ==3711230== by 0x6E9E8A9: ??? (in /usr/lib/libKF5KIOCore.so.5.80.0) ==3711230== by 0x6E9EA5B: KSambaShare::KSambaShare() (in /usr/lib/libKF5KIOCore.so.5.80.0) ==3711230== by 0x6E9EBB5: KSambaShare::instance() (in /usr/lib/libKF5KIOCore.so.5.80.0) ==3711230== by 0x6EA65A6: KFileItem::overlays() const (in /usr/lib/libKF5KIOCore.so.5.80.0) ==3711230== by 0x6DBAD6D: KDirModel::data(QModelIndex const&, int) const (in /usr/lib/libKF5KIOWidgets.so.5.80.0) ==3711230== by 0x604F228: QSortFilterProxyModel::data(QModelIndex const&, int) const (in /usr/lib/libQt5Core.so.5.15.2) ==3711230== Address 0x0 is not stack'd, malloc'd or (recently) free'd but if I don't remember wrong, this is "intentional" that way in the code. -- You are receiving this mail because: You are watching all bug changes.
