On Thursday, August 18, 2011, Martin Heller wrote: > Hi all, > > is it possible to make Helgrind print out stack trace for all threads at > a given moment? > I am debugging a quite complex program (~20 threads) and this would > really help me finding the origins of a deadlock which occurs when > running under Helgrind only (does not occur under gdb, not even under > Memcheck).
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. Do the race reports and lock order violation reports help you figure out where the deadlock is? 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. J ------------------------------------------------------------------------------ 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
