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  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024  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  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Pure Python IOC (CAProcess issue)
From: Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>
To: Simon Reiter <simon.reiter at exp2.physik.uni-giessen.de>
Cc: tech-talk at aps.anl.gov
Date: Thu, 16 Jul 2020 10:29:35 -0700
On 7/16/20 4:03 AM, Simon Reiter via Tech-talk wrote:
> But we ran into some issues by using CAProcess. I already reported this issue on github/pyepics (https://github.com/pyepics/pyepics/issues/210), but it was (highly ;) ) recommended to ask this topic in a bigger round.
> 
> It seems that creating a CAProcess is not always successful, please see the detailed information on github. Somehow stuck at "libca.ca_context_create(ctx)”. The example shown there was only used to disclose and pin down the problem.

Which version(s) of Base have you tested with?

If this is some kind of deadlock, it would be useful to know what
any other threads are doing.  With GDB run "thread apply all backtrace"
and attach the (likely verbose) output.

Are there any special generalTime providers installed (either
current time, or event time)?

FYI. Base >= 7.0.3 has an optimization to skip the locking in
epicsTimeGetCurrent() when no special current time provider
is registered (the common case).

References:
Pure Python IOC (CAProcess issue) Simon Reiter via Tech-talk

Navigate by Date:
Prev: RE: Stream device - general concept how to use Mark Rivers via Tech-talk
Next: Re: Asyn/StreamDevice for HP3458A through Agilent E5810 LAN/GPIB Gateway Hu, Yong via Tech-talk
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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Pure Python IOC (CAProcess issue) Cobb, Tom (DLSLtd,RAL,LSCI) via Tech-talk
Next: Re: Pure Python IOC (CAProcess issue) Michael Davidsaver via Tech-talk
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  <20202021  2022  2023  2024 
ANJ, 17 Jul 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·