> ... > valgrind with --db-aatch I can Ctrl-C and print the backtrace. the > ... > where are the other threads? > ... The --db-attach has several limitations (a.o. it only shows one thread, you can't put breaks, continue, etc).
You can try the 3.7.0 SVN version : this has an integrated gdbserver allowing to fully debug your executable under valgrind (including looking at all threads etc). => you must download and compile the last version from SVN. see http://www.valgrind.org/downloads/repository.html Then you give the option --vgdb-error=0, and you follow the on-screen instructions (if you build the html doc, the Valgrind gdbserver functionalities are documented in a specific section). Note that to investigate deadlocks and/or race conditions, you might try helgrind or drd. (a.o., helgrind has a lock acquisition order verification). Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
