Re: DESC field overflow

[Ralph Lange via Core-talk <core-talk at aps.anl.gov>]

As I said yesterday,

I got the report earlier this week and I will have to verify this.

The report shows a single st.cmd from a test suite that has the IOC booting (with DESC truncated) on an older version of CODAC Core System and has that same IOC bail out (because of DESC being too long) on the recent version.

I will investigate and report.

Thanks for your support!
~Ralph

ps. We are running our semi-annually CODAC Core Hands-On Training course this week (for the 32nd time...). I will need to find time for this.

On Wed, 8 Oct 2025 at 19:00, Johnson, Andrew N. <anj at anl.gov> wrote:

Hi Ralph,

Loading this file into the softIoc

record(ai, test) {

  field(DESC, "This is a long string that will not fit into the field")

}

fails for me on EPICS versions 7.0.9, 7.0.2, 3.15.9 and 3.14.12.8; the softIoc exits immediately with an error. On 3.14.12.5 the error was shown, but the softIoc didn’t exit so presumably following commands in an st.cmd file may have been executed.

A check for the string length in dbPutString() was moved in 106fae3b back in March 2016 (pre-3.14.12.6). Previously a truncated string was copied into the field before the length was checked and the error returned by dbPutString(). Since that commit the field value isn’t set at all, it returns the error code S_dbLib_strLen immediately.

I don’t see how any overly-long DESC field value could have been loaded from a dbLoadRecords command since 3.14.12.6. Are you sure your db-file generation code hasn’t changed and triggered this problem instead?

- Andrew

-- 

Complexity comes for free, Simplicity you have to work for.