> BTW, do you have any idea about "adding the dump of thread info about > all the threads (maybe enabled on/off by a command switch) > when valgrind/memcheck detects serious memory error "?
Distinguishing "serious memory error" from "non-serious memory error" is a problem. > > After fixing the strange repetition of same addresses (numerical address), > which seems to be a bug, or we can simply omit the repetition of the same > numbers after a few times, > the dump will be very useful. This might be something that vgdb can do already. Run "valgrind --help" and search the output for 'vgdb'. The idea is to run valgrind with vgdb so that vgdb gets control at each valgrind error. Then a script tells vgdb what to do, which can include ordinary gdb commands such as "thread all tb" [or whatever the syntax is] to give a traceback for each thread. -- ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
