https://bugs.kde.org/show_bug.cgi?id=393083
Bug ID: 393083
Summary: NOT IMPLEMENTED
Product: valgrind
Version: 3.11.0
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: pentelja...@o2.pl
Target Milestone: ---
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:~$
--
You are receiving this mail because:
You are watching all bug changes.
