EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  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  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: odd libca message printed
From: "Jeff Hill" <[email protected]>
To: "'Chris Slominski'" <[email protected]>, <[email protected]>
Date: Tue, 5 Jul 2005 10:09:34 -0600

Chris,

 

I created entry 207 in the EPICS bug tracker. The failure is reported in the POSIX version of epicsThreadOnceOsd. I suspect that there are orderly shutdown issues (some facility has shutdown prior to when a facility that is using it has shutdown). If you know how to use debuggers and can obtain a stack trace you might be able to speed up the debugging process.

 

Jeff

 

 

-----Original Message-----
From: Chris Slominski [mailto:[email protected]]
Sent: Friday, July 01, 2005 10:38 AM
To: [email protected]
Cc: self
Subject: odd libca message printed

 

I have downloaded EPICS base 3.14.7 and built it under the provided 'hpux-parisc' setting of $EPICS_HOST_ARC. All built fine. I built a test client program that performs a couple channel access fetches and prints the results. The test program works fine when I build against our existing EPICS 3.13.2 installation, but there is a problem running with the newer EPICS version. The program performs the channels access operations correctly, but the signal value prints are sometimes followed by "epicsThreadOnceOsd epicsMutexLock failed" written to the command shell. I suspect the message is generated when I close the channel and exit the program. The number of times the message is written varies from zero to two. More often it is zero, and only once have I seen two. Can anyone explain to me what this message means, and what I need to do to correct it?

 

          Chris Slominski

Thomas Jefferson National Accelerator Facility
Phone:(757) 269-6030 Pager: 584-6030


References:
odd libca message printed Chris Slominski

Navigate by Date:
Prev: RE: UDP send, errno=0x37 Jeff Hill
Next: maybe off topic, maybe not :-) Liyu, Andrei
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: odd libca message printed Chris Slominski
Next: vmivme7050 Ian A Smith
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  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 ·