Re: Pure Python IOC (CAProcess issue)

[Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>]

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).