https://bugs.kde.org/show_bug.cgi?id=373574
Bug ID: 373574
Summary: valgrind: m_syswrap/syswrap-main.c:1938
(vgPlain_client_syscall): Assertion '0 == (sci->flags
& ~(SfPollAfter | SfYieldAfter | SfNoWriteResult))'
failed.
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: kuj...@9livesdata.com
Target Milestone: ---
Created attachment 102745
--> https://bugs.kde.org/attachment.cgi?id=102745&action=edit
code that reproduces described behaviour
When running valgrind with --sim-hints=fuse-compatible we hit into given
assertion.
We checked that in our case sci->flags & SfMayBlock is true.
trace from our original execution (with valgrind with --trace-syscalls=yes):
SYSCALL[28094,1](12) sys_brk ( 0x0 ) --> [pre-success] Success(0x4000000)
--28094-- REDIR: 0x37458176d0 (ld-linux-x86-64.so.2:strlen) redirected to
0x380550c1 (vgPlain_amd64_linux_REDIR_FOR_strlen)
SYSCALL[28094,1](63) sys_newuname ( 0xffefffb10 )[sync] --> Success(0x0)
--28094-- REDIR: 0x37458174e0 (ld-linux-x86-64.so.2:index) redirected to
0x380550db (vgPlain_amd64_linux_REDIR_FOR_index)
SYSCALL[28094,1](89) sys_readlink ( 0x374581b667(/proc/self/exe), 0xffeffec10,
4096 ) --> [pre-success] Success(0x52)
valgrind: m_syswrap/syswrap-main.c:1938 (vgPlain_client_syscall): Assertion '0
== (sci->flags & ~(SfPollAfter | SfYieldAfter | SfNoWriteResult))' failed.
it shows that "sys_readlink" is suspected blocking call. I attach simple code
that reproduces problem when executed by command:
valgrind --tool=memcheck -v --trace-syscalls=yes --sim-hints=fuse-compatible
./sfMayBlockExample.exe
--
You are receiving this mail because:
You are watching all bug changes.
