EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: epicsThreadOnceOsd epicsMutexLock failed
From: Ralph Lange <[email protected]>
To: Wang Xiaoqiang <[email protected]>
Cc: EPICS Tech Talk <[email protected]>
Date: Fri, 16 Apr 2010 11:21:53 -0400
Hello Xiaoqiang,

Please note that the EPICS Base bug tracker has been moved to the new EPICS Base location on Lauchpad, this bug is now:
https://bugs.launchpad.net/epics-base/+bug/541249
The old Mantis tracker is still on-line for reference, but it is *not* updated anymore.


The bug is suspended, because Jeff was asking for a stack trace which was never provided.

The bug is about erroneous behavior experienced on the HP-UX operating system.
Support for HP-UX has been dropped with EPICS release 3.14.9, so this bug will most probably never be fixed.


If you experience the error on a different version of EPICS and a different operating system, please check on Launchpad if it has been reported. If not, you are encouraged to file a new bug report.

Thanks a lot,
Ralph


On Fri 16 Apr 2010 10:08:53 Wang Xiaoqiang wrote:
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 nick.rees
References:
epicsThreadOnceOsd epicsMutexLock failed Wang Xiaoqiang

Navigate by Date:
Prev: epicsThreadOnceOsd epicsMutexLock failed Wang Xiaoqiang
Next: RE: epicsThreadOnceOsd epicsMutexLock failed nick.rees
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: epicsThreadOnceOsd epicsMutexLock failed Wang Xiaoqiang
Next: RE: epicsThreadOnceOsd epicsMutexLock failed nick.rees
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·