Experimental Physics and
Industrial Control System

Benjamin Franksen <[email protected]> · Thu, 24 Nov 2005 02:13:35 +0100

On Thursday 24 November 2005 00:47, Jeff Hill wrote:
> > I am thinking about exporting logClientDestroy (or something
> > similar) to user code. Currently it is a private routine and only
> > executed on exit (via epicsAtExit). I wonder what teh idea was
> > behind the following code (in your original version of
> > logClientDestroy()):
> >
> >     /*
> >      * mutex on (and left on)
> >      */
> >     epicsMutexMustLock (pClient->mutex);
> >     logClientRestart (pClient);
> >     epicsMutexDestroy (pClient->mutex);
> >     free (pClient);
> >
> > Note that logClientRestart signals the restartThread to run, which
> > will eventually call mutexLock.
>
> [...snip...]
>
> > Does that mean when the restartThread calls mutexLock the next time
> > it gets (somehow) shut down automatically? Or does it mean that the
> > thread will hang waiting for the mutex? The Developer's Guide
> > doesn't specify what mutexLock does if the mutex has been
> > destroyed.
>
> In this situation the old code already owned the logClientGlobalMutex
> so the restart thread isn't touching anything important when this is
> running.

Ok, I see (now) where the probem came from. Thanks.

Regarding the rest of your message, I must read this another few times 
and really think hard about it before I can reply anything intelligent.

I wish everyone a tasty turkey :-)

Cheers,
Ben

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System