https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #10 from Christoph Cullmann <cullm...@kde.org> --- Here is the full log of one 3.17.0 run, compiled without any extra flags/patches from the source tarball with the system gcc (GCC) 10.2.0 on Manjaro: # disable PCRE jit export QT_ENABLE_REGEXP_JIT=0 # run the stuff, dies on first QProcess:start call: ./valgrind /makefactory/products/master/release/linux64/a3_c_8939174/bin/a3c --temp-server ==381756== Memcheck, a memory error detector ==381756== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==381756== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==381756== Command: /makefactory/products/master/release/linux64/a3_c_8939174/bin/a3c --temp-server ==381756== ==381756== Syscall param waitid(infop) points to unaddressable byte(s) ==381756== at 0x83EEA9D: syscall (in /usr/lib/libc-2.33.so) ==381756== by 0x7E64010: forkfd (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==381756== by 0x7E4B1D1: QProcessPrivate::startProcess() (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==381756== by 0x7E45E09: QProcessPrivate::start(QFlags<QIODeviceBase::OpenModeFlag>) (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==381756== by 0x15E5E09: main (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/a3c) ==381756== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==381756== ==381796== Warning: invalid file descriptor 183061184 in syscall clone() valgrind: m_syswrap/syswrap-main.c:1957 (vgPlain_client_syscall): Assertion '0 == (sci->flags & ~(SfMayBlock | SfPostOnFail | SfPollAfter))' failed. host stacktrace: ==381796== at 0x58041F1A: show_sched_status_wrk (m_libcassert.c:406) ==381796== by 0x58042037: report_and_quit (m_libcassert.c:477) ==381796== by 0x580421C7: vgPlain_assert_fail (m_libcassert.c:543) ==381796== by 0x5809C76F: vgPlain_client_syscall (syswrap-main.c:1980) ==381796== by 0x58097D1A: handle_syscall (scheduler.c:1208) ==381796== by 0x58099D17: vgPlain_scheduler (scheduler.c:1526) ==381796== by 0x580E8110: thread_wrapper (syswrap-linux.c:101) ==381796== by 0x580E8110: run_a_thread_NORETURN (syswrap-linux.c:154) sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 56 (lwpid 381796) ==381796== at 0x83EEA9D: syscall (in /usr/lib/libc-2.33.so) ==381796== by 0x7E63F86: forkfd (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==381796== by 0x7E4B1D1: QProcessPrivate::startProcess() (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==381796== by 0x7E45E09: QProcessPrivate::start(QFlags<QIODeviceBase::OpenModeFlag>) (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/libQt6Core.so.6) ==381796== by 0x15E5E09: main (in /makefactory/products/master/release/linux64/a3_c_8939174/bin/a3c) client stack range: [0x1FFEFE9000 0x1FFF000FFF] client SP: 0x1FFEFFDDD8 valgrind stack range: [0x10034B8000 0x10035B7FFF] top usage: 8688 of 1048576 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. Fatal: Unable to get port of temporary server before 600 seconds startup timeout. ==381756== ==381756== HEAP SUMMARY: ==381756== in use at exit: 4,185,731 bytes in 30,217 blocks ==381756== total heap usage: 82,652 allocs, 52,435 frees, 172,765,610 bytes allocated ==381756== ==381756== LEAK SUMMARY: ==381756== definitely lost: 256 bytes in 1 blocks ==381756== indirectly lost: 46 bytes in 2 blocks ==381756== possibly lost: 336 bytes in 1 blocks ==381756== still reachable: 4,185,093 bytes in 30,213 blocks ==381756== of which reachable via heuristic: ==381756== newarray : 608 bytes in 4 blocks ==381756== suppressed: 0 bytes in 0 blocks ==381756== Rerun with --leak-check=full to see details of leaked memory ==381756== ==381756== For lists of detected and suppressed errors, rerun with: -s ==381756== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4) -- You are receiving this mail because: You are watching all bug changes.
