Hi Ralph,
I'd like to fix this. There are several threads spawned by various synApps modules. I'll read the 3.15 docs and see how to comply.
Tim Mooney ([email protected]) (630)252-5417
Software Services Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab
________________________________________
From: Ralph Lange [[email protected]]
Sent: Tuesday, September 23, 2014 10:34 AM
To: Mooney, Tim M.
Cc: EPICS Core-Talk
Subject: Autosave and IOC shutdown
Hi Tim,
EPICS 3.15 is trying to make it easier for an IOC to cleanly shutdown.
It add tests and better control over shutdown hooks.
Autosave, on the other hand, starts a thread - running the
save_restore() function - that is designed to never shut down.
That seems like a clear conflict of interests, that shows as frequent
error messages on shutdown:
> A call to 'assert(dbLockIsInitialized)'
> by thread 'save_restore' failed in ../../../src/ioc/db/dbLock.c
> line 255.
> EPICS Release EPICS R3.15.0.1-DEV $$Date$$.
> Local time is 2014-09-23 14:17:13.090976814 UTC
> Please E-mail this message to the author or to [email protected]
> Calling epicsThreadSuspendSelf()
(Autosave trying to use cleaned-up stuff in Base.)
Do you have any thoughts on this?
Cheers,
~Ralph
- References:
- Autosave and IOC shutdown Ralph Lange
- Navigate by Date:
- Prev:
RE: Bug in autosave 5.4 Mooney, Tim M.
- Next:
Fwd: asyn build unsuccessful Prerana Kankiya
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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:
Autosave and IOC shutdown Ralph Lange
- Next:
Fwd: asyn build unsuccessful Prerana Kankiya
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|