EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy
From: Michael Davidsaver <[email protected]>
To: Jameson Graef Rollins <[email protected]>, "Wang Xiaoqiang (PSI)" <[email protected]>
Cc: Epics <[email protected]>
Date: Fri, 15 May 2015 15:50:29 -0400
On 05/15/2015 03:27 PM, Jameson Graef Rollins wrote:
> On Fri, May 15 2015, "Wang Xiaoqiang (PSI)" <[email protected]> wrote:
>> Thanks for the hints. In pcaspy library, the PV instances are created on startup and live until application quits.
>> The casPV::destroy method is not implemented.
>> https://github.com/paulscherrerinstitute/pcaspy/blob/master/pcaspy/pv.cpp#L112
> 
> How is the garbage collection handled?  Since the problem does seem to
> occur when subscriptions are disconnected, presumably something is
> destroyed at that point.

Destruction is just a guess on my part.  I could also be memory corruption.

@Jamie, it would be interesting to re-build with debug symbols for the
C++ code (linux-x86_64-debug).  Then you can inspect the stack frames of
the thread which is having problems.  This might help to answer the
question of which operation caused the problem.

You can also get debug symbols for the python interpreter (python-dbg or
python-debuginfo).  This might give some hints to help with reproducing
the problem.  Also, recent versions of GDB understand python C API calls.


References:
"epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Wang Xiaoqiang (PSI)
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins

Navigate by Date:
Prev: Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
Next: RE: Expected database load times Dalesio, Leo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
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  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·