>... >2243 GST_OBJECT_UNLOCK (pad); >2244 result = GST_PAD_GETCAPSFUNC (pad) (pad); >2245 GST_OBJECT_LOCK (pad); > >The first two snippets use the same lock order and the third snipped >temporarily releases a lock. As line 2243 unlocks pad, there must be another place where pad is locked. This other place might intervene in the cycle of lock acquisition.
> >At the point where the code locks up, I get no complaint from helgrind. >Will try my luck with building 3.7 now. With 3.7.0 SVN, you can try the debugger (cfr --vgdb-error=0) to understand the deadlock under memcheck. You might also try again with helgrind (Julian did several improvements in helgrind, in particular improving the error messages). 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
