Hello -
Recently, I rebuilt a subset of extensions against R3.13.1
(with a little more effort than anticipated - I thought it would
be a matter of changing a few CONFIG files and rebuilding - Not!).
So far, the extensions that we use are all working as before except
for dbst, the tool that checks .db files and strips out unnecessary
lines. I believe dbst is used mostly by people who generate .db
files from CAPFAST schematics via e2db.
The R3.13.1 dbst does not strip out fields that are initialized to
zero. As a result, the .db files it generates are significantly
bigger and IOCs take longer to reboot. Also, it can affect bumpless
reboot if you restore your subroutine/calc inputs before
InitHookafterInitDatabase (the zeros will override what you restore
for these).
Has anybody seen this problem and fixed it? My first guess is that
there is a change to some dbStatic routine that is called by dbst.
Thank you,
Stephanie Allison
- Navigate by Date:
- Prev:
Re: wdTimer & EPICS sequencer Andrew Johnson
- Next:
Re: dbst problem when built against 3.13.1(actually problem with capfast symbols) Rozelle Wright
- 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:
Re: wdTimer & EPICS sequencer Andrew Johnson
- Next:
Re: dbst problem when built against 3.13.1(actually problem with capfast symbols) Rozelle Wright
- 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
|