On Thu, 2015-04-09 at 14:08 -0400, Atalay Ozgovde wrote: > This is essentially the same bug > as:https://bugs.kde.org/show_bug.cgi?id=278057 > > A patch was applied for this bug in version 3.7 and it is considered > fixed. > I am using version 3.10, I confirmed in the source code that the patch > is applied. Valgrind still dread-locks when used to test an > application that uses fuse in our environment. We are using 64bit > Ubuntu 12.04LTS. > > Anybody knows if there is an easy fix? As far as I can see, the 'potentially deadlocking syscall with fuse' have to be marked specially in Valgrind code. If compared to the patch in 3.7, you now have additional syscalls that have to be marked, then that might explain the problem.
Maybe you could discover such syscalls by using --trace-syscalls=yes valgrind option and/or using strace -f valgrind .... and see which syscalls are 'on-going' when the whole stuff deadlocks. Philippe ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
