Re: anyone seen this error

[Andrew Johnson <anj@aps.anl.gov>]

Hi Pierrick,

I don't think EPICS_CA_MAX_ARRAY_BYTES has anything to do with your problem, 
which is being reported by the record support code at record initialization 
time.

Pierrick Hanlet wrote:
> > > I'm using genSubRecord with both input "A" and output "OUTA" fields.
> > > I have the following error:
> > >
> > > Link U - Array too large! 1993313664 Bytes
> > >
> > > which shows up after
> > > iocInit
> > > Starting iocInit
> > > #######################################################################
> > >##### ## EPICS R3.14.10 $R3-14-10$ $2008/10/27 19:39:04$
> > > ## EPICS Base built May 29 2009
> > > #######################################################################
> > >#####
> > >
> > > If I comment out the "field(OUTA" line, I don't get this error.  Has
> > anyone ever seen this?

If you do a
    dbpr "recordname", 2
what are the values reported for the fields FTVU, NOVU and TOVU?

The fact that not setting the OUTA link causes the error to go away implies 
that there may be something rather fundamental wrong with your application, 
and could be caused by your genSub subroutine(s) writing to the wrong place 
in memory.  The ioc command
    dba "recordname.field"
may be helpful because it tells you where the IOC thinks that particular field 
is in memory, which may be different to where your subroutine code thinks it 
is.  If the two are different, you would need to do a 'make rebuild' of your 
application and possibly of your support modules as well.

HTH,

- Andrew
-- 
The best FOSS code is written to be read by other humans -- Harold Welte