On 08/18/2011 05:00 PM, Julian Seward wrote: > No, not really. Sure, it "knows" the stacks of all the threads, > but the problem is that Valgrind runs exactly 1 thread for each > thread in the original program, so there are no other threads around > to "observe" that the system has deadlocked and print the thread > stacks.
Thanks for the answer. In the meantime I have found a partial solution to this problem. I set ulimit -c ulimited run my program under helgrind and then kill it with SIGABRT when it hangs. Using gdb I can then get the stack trace from the vgcore.xxxx file generated. Still it would be a nice feature if Valgrind could just print the stack trace without quitting, for example after being sent SIGUSR signal. > Do the race reports and lock order violation reports help you figure > out where the deadlock is? They do not, there is just one data race (which should be harmless) reported before the deadlock. >From the stack trace I have found out that the deadlock is not due to lock order violation but that all threads are waiting for a condition variable signal which never comes. > btw, if you are using Helgrind, you might want to try the svn trunk > version. It is much improved from the 3.6.x version, in terms of > speed, memory use and error messages. I am already using the svn trunk version. I have installed it after encountering a crash which I described in http://sourceforge.net/mailarchive/message.php?msg_id=27866368 Unfortunately I am far from being able to create a small program to reproduce the crash. Martin Heller ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
