Experimental Physics and Industrial Control System
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
- References:
- RE: R3.14.8 Status/logClient patch Jeff Hill
- Navigate by Date:
- Prev:
RE: R3.14.8 Status/logClient patch Jeff Hill
- Next:
[Fwd: RE: R3.14.8 makeBaseApp.pl] Janet Anderson
- 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: R3.14.8 Status/logClient patch Jeff Hill
- Next:
Re: priorities Marty Kraimer
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024