> From [email protected] Wed Sep 13 20:51 CDT 1995
> Date: Wed, 13 Sep 95 15:48:25 HST
> From: [email protected] (William Lupton)
> To: [email protected]
> Subject: dbGet() problem and exception vector table question
> Content-Type> : > text>
> Content-Length: 1134
>
> Dear all,
>
> We ran into a problem with dbGet() today. It's probably been there for
> ages and is pretty benign _unless_ you happen (by mistake) to have an
> interrupt vector at address zero (in which case your IOC may hang in the
> same way as ours did)!
>
> The problem is that long *perr_status is initialized to NULL and then
> the statement *perr_status = 0 is executed, which overwrites the first
> four bytes of memory with zeroes. All other accesses to *perr_status are
> protected with checks on whether perr_status is NULL (actually I think
> that it can be removed since it always _is_ NULL).
I was shocked when I looked. William is completely correct.
I looked and this bug has been in epics since 3.11.
It will be fixed in the next release.
Marty Kraimer
- Navigate by Date:
- Prev:
Re: Analogue output simulation link SIOL Rozelle Wright
- Next:
mvme162 users... John R. Winans
- 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:
dbGet() problem and exception vector table question William Lupton
- Next:
mvme162 users... John R. Winans
- 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
|