I just discovered the following bug in SNC under epics 3.13:
The sequence program contains the following "for" statement:
for( i=0, j=0; i<1296; i++) {
SNC places the following in the generated *.c file:
for (i = 0; i < 1296; i++) {
Note the j=0 initialization is dropped. Needless to say, nothing good happens
when a statement such as:
FilledBuckets[j++] = i;
is within the "for" loop;i.e, memory is sequentially trashed as j gets
incremented.
The SNC under epics 3.12 generated the correct c code.
The question:
Is there a way to identify unconnected process variables in a sequence
program without stepping through every channel using seqChanShow? This
gets pretty laborious when a state program has lots of pv's (100 - 200).
Frank
- Replies:
- Re: SNC bug and question Peregrine McGehee
- Navigate by Date:
- Prev:
developing Gpib devSupport mauro
- Next:
Bookmark to EPICS software distribution Bakul Banerjee
- 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:
developing Gpib devSupport mauro
- Next:
Re: SNC bug and question Peregrine McGehee
- 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
|