[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
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 GIL). So code that works by accident because one thread 'always' does something before another can get caught out. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
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 with some test cases and not others. I can't see any pattern behind which test cases hang and which don't. Is there any way that valgrind could introduce a deadlock? Perhaps the read from /dev/fuse triggers a signal, but the signal handler can't run because the first thread is blocked in the fspacectl syscall? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
https://bugs.kde.org/show_bug.cgi?id=480052 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Paul Floyd --- The missing syscall should be fixed with commit 3cacde0ca261196031cb84b22ad427483bae057e (HEAD -> master, origin/master, origin/HEAD) Author: Paul Floyd Date: Sat Jan 20 21:14:37 2024 +0100 Bug 480052 - WARNING: unhandled amd64-freebsd syscall: 580 I still get a lot of errors and the googletest fails -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
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.
[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
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 all bug changes.
[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
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 *rqsr,
int flags,
_Out_opt_ struct spacectl_range *rmsr,
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
https://bugs.kde.org/show_bug.cgi?id=480052 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
