Experimental Physics and
Industrial Control System

Hi, folks.  We recently saw the following error thrown from one of our
dual pyepics/pcaspy applications:

epicsMutex pthread_mutex_unlock failed: error Invalid argument
epicsMutexOsdUnlockThread _main_ (0x2999f20) can't proceed, suspending.

After this error was thrown the application became completely
unresponsive and had to be manually killed.

I'm not sure which interface the error came from: pcaspy or pyepics.
We're running the following versions of the relevant packages:

epics-base 3.14.12.2
pyepics 3.2.0
pcaspy 0.4.1

Any idea what could have caused it?  I've only found one reference to a
similar issue with a gateway (base 3.14.9, gateway 2.0.3.0) [0].  A
follow-up bug report implied that the issue might have been addressed in
base 3.14.11 [1], which precedes the version we're using.

Any help would be much appreciated.  Thanks so much.

jamie.

[0] http://www.aps.anl.gov/epics/tech-talk/2009/msg00021.php
[1] https://bugs.launchpad.net/epics-base/+bug/541356

Attachment: signature.asc
Description: PGP signature

Replies:

Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver

Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins

Navigate by Date:

Prev: Re: using EPICS code with HTTP port Jack

Next: CSS - subarray display bug Amien Crombie [TLABS]

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <2015>  2016  2017  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Regarding EPICS EDM-1-12-98 Rahul Jain

Next: Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <2015>  2016  2017  2018  2019  2020  2021  2022  2023  2024