Experimental Physics and Industrial Control System

On 11/17/2014 06:24 PM, Benjamin Franksen wrote:
> ...
>> Since you are running the latest, can you arrange to set the global
>> variable atExitDebug=1 (defined in epicsExit.c)?  This should give some
>> clue about where in the exit sequence things are crashing.
> 
> It ends now with:
> 
> ...as before...
>     Results
>     =======
>        Tests: 24
>       Passed:  24 = 100.00%
> Instance 0 of sequencer program "bittypesTest" terminated
> atExit 0x4055f0((nil))
> atExit dbProcessNotifyExit((nil))


Ok, so I ran your unittest :) and see the same.  I think this is an
actual bug which arises because dbProcessNotifyExit() doesn't block
until pending operations complete.

In this case the pending operation arising from seq_pvPut() as CA put
with callback operations now use dbNotify in 3.15.


Michael

References:

3.15.0.2: Shutdown issues Ralph Lange

Re: 3.15.0.2: Shutdown issues Benjamin Franksen

Re: 3.15.0.2: Shutdown issues Michael Davidsaver

Re: 3.15.0.2: Shutdown issues Benjamin Franksen

Navigate by Date:

Prev: Jenkins build is back to normal : epics-base-3.15-win64s #99 APS Jenkins

Next: Jenkins build is back to normal : epics-base-3.15-win32s #98 APS Jenkins

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: 3.15.0.2: Shutdown issues Benjamin Franksen

Next: Re: 3.15.0.2: Shutdown issues Benjamin Franksen

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <2014>  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024