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