On 05/13/2015 05:20 PM, Mark Rivers wrote:
> One suggestion would be to try the latest base 3.14 release, 3.14.12.5. The 3.14.12.2 version you are running is 3.5 years old, and there have been a number of bug fixes.
There was only one "substantial" change to src/cas/ between 3.14.12.2
and .5.
https://bazaar.launchpad.net/~epics-core/epics-base/3.14/revision/12382
Aside from the addition of caServer::propertyEventMask() this is all
whitespace change.
So if 3.14.12.5 makes a difference then the problem isn't PCAS.
- 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 Mark Rivers
- Navigate by Date:
- Prev:
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
- Next:
Problems building on Cygwin Mark Rivers
- 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:
RE: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Mark Rivers
- 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
|