Aloha,
Consider a select record with SELM == "Specified" (SELECTED in the code).
The select record initializes non-constant inputs to 1e+30 . Then on
processing, only the selected input is fetched (contrary to the
documentation). That leaves non-selected links as 1e+30 . Then if one
tries a dbpr on that record, on a SPARC at least, one gets a floating point
exception in dbStatic/dbStaticRun.c:realToString at intval=value; . Since
that may happen on other architectures too, it seems like a check against
MAXINT is warranted around the easy integer case?
Jim
- Replies:
- Re: select record versus dbpr() versus SPARC (at least) Marty Kraimer
- Re: select record versus dbpr() versus SPARC (at least) Benjamin Franksen
- Navigate by Date:
- Prev:
Work in sunny California Chestnut, Ronald P.
- Next:
Re: select record versus dbpr() versus SPARC (at least) Marty Kraimer
- 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:
Work in sunny California Chestnut, Ronald P.
- Next:
Re: select record versus dbpr() versus SPARC (at least) Marty Kraimer
- 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
|