EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: breaktable checks in dbLexRoutines.c in 3.14.9
From: Andrew Johnson <[email protected]>
To: Steven Hartman <[email protected]>
Cc: EPICS tech-talk <[email protected]>
Date: Mon, 13 Aug 2007 13:53:36 -0500
Hi Steve,

Steven Hartman wrote:

Yes, such an approach could be acceptable. However, would it be possible to also have a way to over-ride the default behavior at build time? The breakpoint table dbd currently gets rejected during the make process by dbExpand.

I did mention that this would be the case in an earlier message, when I recommended that you move your breakpoint tables into a separate DBD file which you load independently at runtime. If you want a different default value for the dbBptNotMonotonic you can always alter your copy of base however you like, but I don't want the official version of base to skip this check unless explicitly told to do so by someone like yourself who understands the issues, and unfortunately there's no easy way to make that happen conditionally when running dbExpand.


Breakpoint tables actually hold a different kind of content than any of the other DBD entries (which are all metadata), and as a result I could very easily see them being moved into a different kind of file at some point in the future. If we do that we'd definitely make them reloadable at runtime, which may work right now but is not thread-safe IIRC. As a result splitting the tables into their own DBD file(s) now might just save you from having to do it later.

Actually it should be possible to include breakpoint table data in a .db file today â VDCT won't handle them properly, but this might be a better place for them conceptually and the msi tool that does template substitutions at build-time won't reject a non-monotonic breaktable like dbExpand does.

HTH,

- Andrew
--
When a distinguished but elderly scientist states that something is
possible, he is almost certainly right.  When he states that something
is impossible, he is very probably wrong.  -- Arthur C. Clarke

References:
breaktable checks in dbLexRoutines.c in 3.14.9 Steven Hartman
Re: breaktable checks in dbLexRoutines.c in 3.14.9 Andrew Johnson
Re: breaktable checks in dbLexRoutines.c in 3.14.9 Steven Hartman
Re: breaktable checks in dbLexRoutines.c in 3.14.9 Dirk Zimoch
Re: breaktable checks in dbLexRoutines.c in 3.14.9 Andrew Johnson

Navigate by Date:
Prev: Re: "build" make target now installs Tim Mooney
Next: Medm for cygwin White, Glen Russell
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: breaktable checks in dbLexRoutines.c in 3.14.9 Andrew Johnson
Next: "build" make target now installs mcallister
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·