Experimental Physics and Industrial Control System
Hi,
When CA client exit, sometimes it spills out "epicsThreadOnceOsd
epicsMutexLock failed" message. It has been reported since 3.14.7 and
has an entry 207 in Mantis. The status is labeled as "suspended". Does
it mean it is hopeless to be solved?
http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=207
In normal cases it is harmless since the program is anyway exiting.
However it exits with code 255. If it is run as a subprocess, this will
cause the caller think exit code other than 0 is wrong and stop
execution. In such case one cannot ignore the exit code, which would
ignore other possible exceptions.
Thanks and nice weekend.
--
Dr. Xiaoqiang Wang
Paul Scherrer Institut, WBGB/010
5232 Villigen PSI, Switzerland
- Replies:
- Re: epicsThreadOnceOsd epicsMutexLock failed Ralph Lange
- Navigate by Date:
- Prev:
How to compile the sysVmeMapShow() function to the MVME5500 BSP? 周永年
- Next:
Re: epicsThreadOnceOsd epicsMutexLock failed Ralph Lange
- 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: How to compile the sysVmeMapShow() function to the MVME5500 BSP? Andrew Johnson
- Next:
Re: epicsThreadOnceOsd epicsMutexLock failed Ralph Lange
- 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