On 05/13/2015 01:06 PM, Jameson Graef Rollins wrote:
> On Tue, May 12 2015, Michael Davidsaver <[email protected]> wrote:
>> ...
> Hi, Michael. I should have mentioned that I did try doing this at your
> suggestion, but wasn't able to devine anything useful myself. I'm not
> quite sure what I'm looking for, though:
The error is coming from:
http://bazaar.launchpad.net/~epics-core/epics-base/3.14/view/head:/src/libCom/osi/os/posix/osdMutex.c#L108
If the unlock fails then cantProceed() is called, which calls
epicsThreadSuspendSelf. The posix version of which ultimately calls
pthread_cond_wait().
http://bazaar.launchpad.net/~epics-core/epics-base/3.14/view/head:/src/libCom/osi/os/posix/osdEvent.c#L75
>From the top two frames this could be either thread #1 or #4. Can you
post the full stacks?
Michael
- Replies:
- Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- 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
- Navigate by Date:
- Prev:
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- Next:
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- 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 Jameson Graef Rollins
- Next:
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- 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
|