https://bugs.kde.org/show_bug.cgi?id=480052
--- Comment #6 from Paul Floyd ---
Valgrind is unlikely to cause a deadlock.
However, it can bring out race conditions. Firstly, it is considerably slower.
Secondly, it runs effectively as though there were a single CPU (similar to
Python and its
https://bugs.kde.org/show_bug.cgi?id=480052
--- Comment #5 from asom...@gmail.com ---
Thanks for the quick fix! It works for me. As for the other failures, they
seem unrelated. It seems like the server thread (there are two threads) hangs
when reading from /dev/fuse. The hangs only happen
https://bugs.kde.org/show_bug.cgi?id=480052
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=480052
--- Comment #3 from Paul Floyd ---
Bah yes. Syscall 580 was a hole in the numbering until FreeBSD 14.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480052
--- Comment #2 from asom...@gmail.com ---
No, it isn't in 13.1. It first appeared in 14.0. You can check from the man
pages browser here: https://man.freebsd.org/cgi/man.cgi?query=fspacectl .
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=480052
--- Comment #1 from Paul Floyd ---
This should be in FreeBSD 13.1+
580 AUE_FSPACECTL STD|CAPENABLED {
int fspacectl(
int fd,
int cmd,
_In_ const struct spacectl_range
https://bugs.kde.org/show_bug.cgi?id=480052
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
