Subject: |
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy |
From: |
Michael Davidsaver <[email protected]> |
To: |
[email protected] |
Date: |
Tue, 12 May 2015 16:29:59 -0400 |
On 05/12/2015 02:48 PM, Jameson Graef Rollins wrote:
> The most troubling aspect of the problem is that the actual PVs remain
> active, while the underlying process freezes. Existing PV subscriptions
> remain valid and the PCAS continues to respond to new requests. However
> the database is no longer being updated so all values are bogus. In
> other words, we have **no external indication that the process is in a
> frozen state**.
Since the process continues running can you attached gdb and get stack
traces? This should show the place where the _main_ thread has stopped.
> $ gdb
> (gdb) attach <pid>
> (gdb) thread apply all backtrace
- 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
- Navigate by Date:
- Prev:
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Wang Xiaoqiang (PSI)
- Next:
problem about IPServerPort using ASYN bella
- 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
|