[valgrind] [Bug 407313] Deadlock when syscall is handled in other thread

2019-05-07 Thread Falk Werner
https://bugs.kde.org/show_bug.cgi?id=407313 --- Comment #5 from Falk Werner --- Thanks a lot, --sim-hints=fuse-compatible solves the issue. I was not aware, that such a flag exists. I will spend more effort in investigation next time. Sorry for inconvience. -- You are receiving this mail

[valgrind] [Bug 407313] Deadlock when syscall is handled in other thread

2019-05-07 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=407313 Tom Hughes changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[valgrind] [Bug 407313] Deadlock when syscall is handled in other thread

2019-05-07 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=407313 --- Comment #3 from Tom Hughes --- The answer appears to be sys_newstat: SYSCALL[10855,1](4) sys_newstat ( 0x4ea48e0(/tmp/libfuse_test_LKz1UA), 0x1ffefff1a0 ) Which by the looks of it has not been marked as potentially blocking. I think we've been

[valgrind] [Bug 407313] Deadlock when syscall is handled in other thread

2019-05-07 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=407313 --- Comment #2 from Tom Hughes --- Also, the valgrind output would be more useful that the strace. Make sure you include --trace-syscalls=yes at a minimu, -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 407313] Deadlock when syscall is handled in other thread

2019-05-07 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=407313 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes