Subject: |
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy |
From: |
Michael Davidsaver <[email protected]> |
To: |
[email protected] |
Date: |
Tue, 24 Feb 2015 08:33:39 -0500 |
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.
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>
- Replies:
- Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
- References:
- "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- Navigate by Date:
- Prev:
Re: Importing cs-studio into eclipse Xinyu.Wu
- Next:
Support for an HPLC pump manufactured by SSI tom.cobb
- 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:
"epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- 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
|