Experimental Physics and
Industrial Control System

Michael Davidsaver via Core-talk <[email protected]> · Wed, 3 Apr 2019 09:31:24 -0700

On 4/2/19 2:35 PM, Konrad, Martin via Core-talk wrote:
> Hi,
> I have a bunch of unit tests for support modules that spawn epicsThreads
> and tear them down after a very short time. I noticed that although I'm
> waiting for the thread to shut down cleanly tests are not reproducible.
> In the attached simple code snipped I sometimes see the thread function
> running:

In situations like this I use an epicsEvent, and trigger it at
the start of run().  The main thread would then wait on this
event to detect actual thread start.

> $ time ./a.out
> myThread::myThread() begin
> myThread::myThread() end
> myThread::~myThread() begin
> myThread::run() begin
> myThread::run() end
> myThread::~myThread() end
> 
> real    0m8.044s
> user    0m0.025s
> sys     0m0.024s
> 
> However, sometimes the destructor gets called so fast that the thread
> function doesn't run:
> 
> $ time ./a.out
> myThread::myThread() begin
> myThread::myThread() end
> myThread::~myThread() begin
> myThread::~myThread() end
> 
> real    0m5.041s
> user    0m0.014s
> sys     0m0.031s
> 
> I'm wondering if there is a way I can ensure run() always runs. I'm
> wondering if making the constructor wait until run() actually starts
> executing.
> 
> Thanks,
> 
> Martin
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System