https://bugs.kde.org/show_bug.cgi?id=449838
--- Comment #8 from Daniele ---
thank you for fixing the bug
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449838
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=449838
--- Comment #6 from Daniele ---
I think there is no name behind that fd, the fd are returned from
io_uring_setup systemcall
https://manpages.debian.org/unstable/liburing-dev/io_uring_setup.2.en.html
it will definitely be fine until someone complains
https://bugs.kde.org/show_bug.cgi?id=449838
--- Comment #5 from Mark Wielaard ---
(In reply to Daniele from comment #4)
> yes with--track-fds=no valgrind not crash
>
> for reproduce you need only to call io_uring_queue_init()
> https://pastebin.com/MzFxQGmb
Thanks. I think the solution is
https://bugs.kde.org/show_bug.cgi?id=449838
--- Comment #4 from Daniele ---
yes with--track-fds=no valgrind not crash
for reproduce you need only to call io_uring_queue_init()
https://pastebin.com/MzFxQGmb
log
https://pastebin.com/eEYqmMAe
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=449838
--- Comment #3 from Mark Wielaard ---
(In reply to Daniele from comment #2)
> isolate bug need time, but can try
>
> --trace-syscalls=yes
> LOG
> [...]
> SYSCALL[7498,1](425) sys_io_uring_setup ( 0x1000, 137422177456 )[sync] -->
> Success(0x3)
https://bugs.kde.org/show_bug.cgi?id=449838
--- Comment #2 from Daniele ---
isolate bug need time, but can try
--trace-syscalls=yes
LOG
***
==7498== Memcheck, a memory error detector
==7498== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==7498== Using Valgrind-3.18.1 and
https://bugs.kde.org/show_bug.cgi?id=449838
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
