==1124== Memcheck, a memory error detector
==1124== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1124== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==1124== Command: ./valgrind_qprocess
==1124== Parent PID: 1073
==1124== 
==1124== Syscall param waitid(infop) points to unaddressable byte(s)
==1124==    at 0x5212D5D: syscall (in /usr/lib/libc-2.32.so)
==1124==    by 0x4AAC277: ??? (in /usr/lib/libQt5Core.so.5.15.1)
==1124==    by 0x4A9023B: ??? (in /usr/lib/libQt5Core.so.5.15.1)
==1124==    by 0x109382: main (main.cpp:9)
==1124==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==1124== 
==1125== 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:
==1125==    at 0x58041B2A: show_sched_status_wrk (m_libcassert.c:406)
==1125==    by 0x58041C47: report_and_quit (m_libcassert.c:477)
==1125==    by 0x58041DD7: vgPlain_assert_fail (m_libcassert.c:543)
==1125==    by 0x5809AB4F: vgPlain_client_syscall (syswrap-main.c:1980)
==1125==    by 0x5809617A: handle_syscall (scheduler.c:1208)
==1125==    by 0x58098177: vgPlain_scheduler (scheduler.c:1526)
==1125==    by 0x580E38D0: thread_wrapper (syswrap-linux.c:101)
==1125==    by 0x580E38D0: run_a_thread_NORETURN (syswrap-linux.c:154)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable syscall 56 (lwpid 1125)
==1125==    at 0x5212D5D: syscall (in /usr/lib/libc-2.32.so)
==1125==    by 0x4AAC1FD: ??? (in /usr/lib/libQt5Core.so.5.15.1)
==1125==    by 0x4A9023B: ??? (in /usr/lib/libQt5Core.so.5.15.1)
==1125==    by 0x109382: main (main.cpp:9)
client stack range: [0x1FFEFFD000 0x1FFF000FFF] client SP: 0x1FFF000608
valgrind stack range: [0x1002AA6000 0x1002BA5FFF] top usage: 13424 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.

==1124== 
==1124== HEAP SUMMARY:
==1124==     in use at exit: 19,092 bytes in 12 blocks
==1124==   total heap usage: 227 allocs, 215 frees, 137,539 bytes allocated
==1124== 
==1124== LEAK SUMMARY:
==1124==    definitely lost: 0 bytes in 0 blocks
==1124==    indirectly lost: 0 bytes in 0 blocks
==1124==      possibly lost: 0 bytes in 0 blocks
==1124==    still reachable: 19,092 bytes in 12 blocks
==1124==         suppressed: 0 bytes in 0 blocks
==1124== Rerun with --leak-check=full to see details of leaked memory
==1124== 
==1124== For lists of detected and suppressed errors, rerun with: -s
==1124== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)