Experimental Physics and
Industrial Control System

Mark Rivers via Core-talk <[email protected]> · Fri, 10 Jan 2020 21:05:20 +0000

> 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

That's a good point, but I don't see how it relates my current issue.  As I said, I am getting these warning messages at iocInit when I first create the asynPortDriver object, long before I want to destroy it.

Why am I getting these messages?

Mark

-----Original Message-----
From: Konrad, Martin <[email protected]> 
Sent: Friday, January 10, 2020 2:42 PM
To: Mark Rivers <[email protected]>
Cc: [email protected]
Subject: Re: epicsThread warnings

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]

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System