Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy

[Michael Davidsaver <mdavidsaver@bnl.gov>]

On 02/24/2015 08:33 AM, Michael Davidsaver wrote:
> 
> 
> On 02/24/2015 02:59 AM, Jameson Graef Rollins wrote:
>> ...
>> epicsMutex pthread_mutex_unlock failed: error Invalid argument
>> epicsMutexOsdUnlockThread _main_ (0x2999f20) can't proceed, suspending.
>> ...
> 
> This is a familiar symptom to me as a few of these have been found and
> fixed in Base 3.15.  The question is where this specifically error comes
> from.

Oops, I mis-read your error as pthread_mutex_destroy().  Invalid
argument for pthread_mutex_unlock() is almost certainly memory
corruption.  So running valgrind is still a good idea.


> If you run your program in valgrind it should show the full stack trace
> where the error occurs.  Try
> 
>> $ valgrind <program> <args>
> 
> and
> 
>> $ valgrind --tool=helgrind <program> <args>