lsd@lsd-K56CB:~$ valgrind /usr/bin/flatpak run --branch=master --arch=x86_64 --command=q2pro com.github.skullernet.q2pro ==13484== Memcheck, a memory error detector ==13484== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==13484== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==13484== Command: /usr/bin/flatpak run --branch=master --arch=x86_64 --command=q2pro com.github.skullernet.q2pro ==13484== valgrind: m_syswrap/syswrap-linux.c:5361 (vgSysWrap_linux_sys_fcntl_before): Assertion 'Unimplemented functionality' failed. valgrind: valgrind host stacktrace: ==13484== at 0x38083F48: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==13484== by 0x38084064: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==13484== by 0x380841F1: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==13484== by 0x380FB399: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==13484== by 0x380D6234: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==13484== by 0x380D2D2A: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==13484== by 0x380D43DE: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==13484== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 13484) ==13484== at 0x6DE8687: do_fcntl (fcntl.c:31) ==13484== by 0x6DE8687: fcntl (fcntl.c:71) ==13484== by 0x16F23D: ??? (in /usr/bin/flatpak) ==13484== by 0x144087: ??? (in /usr/bin/flatpak) ==13484== by 0x15E49A: ??? (in /usr/bin/flatpak) ==13484== by 0x1627C7: ??? (in /usr/bin/flatpak) ==13484== by 0x12FC19: ??? (in /usr/bin/flatpak) ==13484== by 0x122BEC: ??? (in /usr/bin/flatpak) ==13484== by 0x701582F: (below main) (libc-start.c:291) 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. lsd@lsd-K56CB:~$
Can you please run with --trace-syscalls=yes and paste in the last few lines leading up to the error?
(In reply to Tom Hughes from comment #1) > Can you please run with --trace-syscalls=yes and paste in the last few lines > leading up to the error? lsd@lsd-K56CB:~$ valgrind /usr/bin/flatpak run --branch=master --arch=x86_64 --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro ==10083== Memcheck, a memory error detector ==10083== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==10083== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==10083== Command: /usr/bin/flatpak run --branch=master --arch=x86_64 --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro ==10083== błąd: Unknown option --trace-syscalls=yes ==10083== ==10083== HEAP SUMMARY: ==10083== in use at exit: 62,631 bytes in 658 blocks ==10083== total heap usage: 2,827 allocs, 2,169 frees, 366,245 bytes allocated ==10083== ==10083== LEAK SUMMARY: ==10083== definitely lost: 96 bytes in 1 blocks ==10083== indirectly lost: 58 bytes in 1 blocks ==10083== possibly lost: 1,480 bytes in 19 blocks ==10083== still reachable: 60,853 bytes in 635 blocks ==10083== of which reachable via heuristic: ==10083== length64 : 816 bytes in 18 blocks ==10083== newarray : 1,632 bytes in 22 blocks ==10083== suppressed: 0 bytes in 0 blocks ==10083== Rerun with --leak-check=full to see details of leaked memory ==10083== ==10083== For counts of detected and suppressed errors, rerun with: -v ==10083== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) lsd@lsd-K56CB:~$
(In reply to penteljapan from comment #2) > (In reply to Tom Hughes from comment #1) > > Can you please run with --trace-syscalls=yes and paste in the last few lines > > leading up to the error? > > lsd@lsd-K56CB:~$ valgrind /usr/bin/flatpak run --branch=master --arch=x86_64 > --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro > ==10083== Memcheck, a memory error detector > ==10083== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==10083== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info > ==10083== Command: /usr/bin/flatpak run --branch=master --arch=x86_64 > --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro > ==10083== > błąd: Unknown option --trace-syscalls=yes > ==10083== > ==10083== HEAP SUMMARY: > ==10083== in use at exit: 62,631 bytes in 658 blocks > ==10083== total heap usage: 2,827 allocs, 2,169 frees, 366,245 bytes > allocated > ==10083== > ==10083== LEAK SUMMARY: > ==10083== definitely lost: 96 bytes in 1 blocks > ==10083== indirectly lost: 58 bytes in 1 blocks > ==10083== possibly lost: 1,480 bytes in 19 blocks > ==10083== still reachable: 60,853 bytes in 635 blocks > ==10083== of which reachable via heuristic: > ==10083== length64 : 816 bytes in 18 blocks > ==10083== newarray : 1,632 bytes in 22 > blocks > ==10083== suppressed: 0 bytes in 0 blocks > ==10083== Rerun with --leak-check=full to see details of leaked memory > ==10083== > ==10083== For counts of detected and suppressed errors, rerun with: -v > ==10083== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) > lsd@lsd-K56CB:~$ ---------------------------------- lsd@lsd-K56CB:~$ valgrind /usr/bin/flatpak run --branch=master --arch=x86_64 --command=q2pro com.github.skullernet.q2pro ==10176== Memcheck, a memory error detector ==10176== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==10176== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==10176== Command: /usr/bin/flatpak run --branch=master --arch=x86_64 --command=q2pro com.github.skullernet.q2pro ==10176== ==10176== Warning: unimplemented fcntl command: 1033 błąd: fcntl(F_ADD_SEALS): Zły argument ==10176== ==10176== HEAP SUMMARY: ==10176== in use at exit: 86,276 bytes in 1,118 blocks ==10176== total heap usage: 8,712 allocs, 7,594 frees, 1,058,004 bytes allocated ==10176== ==10176== LEAK SUMMARY: ==10176== definitely lost: 120 bytes in 2 blocks ==10176== indirectly lost: 1,974 bytes in 38 blocks ==10176== possibly lost: 1,616 bytes in 20 blocks ==10176== still reachable: 82,030 bytes in 1,053 blocks ==10176== of which reachable via heuristic: ==10176== length64 : 1,080 bytes in 24 blocks ==10176== newarray : 1,696 bytes in 26 blocks ==10176== suppressed: 0 bytes in 0 blocks ==10176== Rerun with --leak-check=full to see details of leaked memory ==10176== ==10176== For counts of detected and suppressed errors, rerun with: -v ==10176== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) lsd@lsd-K56CB:~$
(In reply to penteljapan from comment #2) > (In reply to Tom Hughes from comment #1) > > Can you please run with --trace-syscalls=yes and paste in the last few lines > > leading up to the error? > > lsd@lsd-K56CB:~$ valgrind /usr/bin/flatpak run --branch=master --arch=x86_64 > --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro > ==10083== Memcheck, a memory error detector > ==10083== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==10083== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info > ==10083== Command: /usr/bin/flatpak run --branch=master --arch=x86_64 > --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro > ==10083== > błąd: Unknown option --trace-syscalls=yes The --trace-syscalls=yes should be given to Valgrind, not to your application.
Thanks for help and wait, everthing its ok with that wonder . CLOSING