Michael,
There can be many CA contexts in a system; In fact, as Mark has discovered, for backwards compatibility reasons the first call to the CA library implicitly creates a CA context for the current thread. Several threads can also agree together to share a CA context. If the ca_create_context fails it returns failure status.
epicsShareFunc int epicsShareAPI ca_context_create (enum ca_preemptive_callback_select select);
In an IOC, by default only the threads associated with the DB CA links and the sequencer maintain CA contexts; for good reasons those two contexts are separate and independent BTW. There is no CA context associated with the startup script, the EPICS shell, or the vxWorks shell although if you called a CA function from those threads a CA context would be implicitly created but this typically isn't a good idea.
Jeff
> -----Original Message-----
> From: [email protected] [mailto:tech-talk-
> [email protected]] On Behalf Of [email protected]
> Sent: Friday, April 19, 2013 7:44 AM
> To: [email protected]
> Subject: Calling ca_context_create(1) too late
>
> I've just discovered that calling ca_context_create(1) after iocInit() appears to
> succeed (it returns ECA_NORMAL) ... but the resulting context is not very
> healthy! In my particular case I find that ca_array_get_callback delivers zero
> length data, but I expect other deeper problems are to be found.
>
> I understand that I need to call ca_context_create() a good deal earlier, but I
> don't really understand why it appears to succeed -- is it possible for an error
> code to be returned instead, please? (In some future version of EPICS, I'm
> testing this on 3.14.11.)
>
> Alternatively, is there some reliable way I can test whether it has succeeded?
> I don't have full control over when my library is initialised, so detecting an
> error immediately would be more friendly to the user.
>
> --
> This e-mail and any attachments may contain confidential, copyright and or
> privileged material, and are for the use of the intended addressee only. If you
> are not the intended addressee or an authorised recipient of the addressee
> please notify us of receipt by returning the e-mail and do not use, copy,
> retain, distribute or disclose the information in or attached to the e-mail.
> Any opinions expressed within this e-mail are those of the individual and not
> necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> attachments are free from viruses and we cannot accept liability for any
> damage which you may sustain as a result of software viruses which may be
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England
> and Wales with its registered office at Diamond House, Harwell Science and
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
>
>
>
- References:
- Calling ca_context_create(1) too late michael.abbott
- Navigate by Date:
- Prev:
Re: genesys power supply IOC James F Ross
- Next:
Re: genesys power supply IOC Jiro Fujita
- 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
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Calling ca_context_create(1) too late Andrew Johnson
- Next:
FW: Calling ca_context_create(1) too late michael.abbott
- 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
2020
2021
2022
2023
2024
|