Experimental Physics and
Industrial Control System

Hi Mark,
> I don't actually ever delete the asynPortDriver object, so I never
> call the callbackThread destructor.
Yeah, you should certainly do that. See [1] for an example of how I
construct a driver object (note that I'm using emplace() here since
asynPortDriver objects can't be copy constructed). I'm storing my driver
objects together with the device name in a map [2] to support IOC shell
functions on a per-port basis (e.g. turn on debugging output only for a
certain port). I'm destroying the whole list when atExit calls my
cleanUp function [3].

HTH,

Martin

[1]
https://github.com/mark0n/drvFGPDB/blob/release/fc3/drvFGPDBApp/src/drvFGPDB_IOC.cpp#L92-L95
[2]
https://github.com/mark0n/drvFGPDB/blob/release/fc3/drvFGPDBApp/src/drvFGPDB_IOC.cpp#L28
[3]
https://github.com/mark0n/drvFGPDB/blob/release/fc3/drvFGPDBApp/src/drvFGPDB_IOC.cpp#L156

-- 
Martin Konrad
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: [email protected]

Replies:

RE: epicsThread warnings Mark Rivers via Core-talk

References:

epicsThread warnings Mark Rivers via Core-talk

Re: epicsThread warnings Konrad, Martin via Core-talk

Navigate by Date:

Prev: RE: epicsThread warnings Mark Rivers via Core-talk

Next: RE: epicsThread warnings Mark Rivers via Core-talk

Index: 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: epicsThread warnings Mark Rivers via Core-talk

Next: RE: epicsThread warnings Mark Rivers via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024