RE: Problems with asyn read calls at driver exit

[Sergio Esquembri <sesquembri@i2a2.upm.es>]

Thanks Mark.

I have applied that and its working for the moment.

Sergio Esquembri
Technical University of Madrid

El 2015-05-28 14:46, Mark Rivers escribió:
> One way that this is commonly done is to have your epicsAtExit handler
> set a flag epicsExiting=true.  Then at the top of your I/O functions
> you just return immediately if epicsExiting==true.
>
> Mark
>
> ________________________________________
> From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on
> behalf of Sergio Esquembri [sesquembri@i2a2.upm.es]
> Sent: Thursday, May 28, 2015 8:39 AM
> To: tech-talk@aps.anl.gov
> Subject: Problems with asyn read calls at driver exit
>
> Hi,
>
> I'm developing an EPICS driver using asynDriver and I'm having problems
> with the finalization of the driver. The function that frees all the
> resources allocated and closes the session with the hardware driver is
> registered with epicsAtExit. The problem here is that some PVs have
> timed scans and the driver is receiving calls to the registered read
> methods after the ioc exit call.
>
> What is the best way to avoid read calls when closing the driver?
> Should I unregister manually my driver from the asyn interfaces?
>
> Any help or hint about this will be appreciated.
>
> Thanks,
> Sergio.
>
> --
> -----------------------------