IOCSH commands stopped echoing

Bug #1741578 reported by Andrew Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Status tracked in 7.0
3.16
Fix Released
Medium
Andrew Johnson
7.0
Fix Released
Medium
Andrew Johnson

Bug Description

Mark Rivers reported that a VxWorks startup script which switches to iocsh for some commands stops echoing those commands with EPICS 7, although the prompts are still displayed for each line.

I simplified his report to loading this script after booting an IOC:

# Echo test
iocsh
# Comment
exit
# End test

Under 3.15.5:

iocanj> < echo.cmd
# Echo test
iocsh
epics> # Comment
epics> exit
value = 0 = 0x0
# End test

Under 7.0.1:

iocanj> < echo.cmd
# Echo test
iocsh
epics> epics> value = 0 = 0x0

Revision history for this message
Andrew Johnson (anj) wrote :

Also affects Base-3.16.1.

It seems that we actually stopped building the VxWorks-specific implementation of the readline code that calls ledLib, thus on VxWorks we're currently only using the basic implementation with no line editing or command-line history. This was due to a missing build configuration parameter when I reorganized the epicsReadline code (there is also a typo in the vxWorks/osdReadline.c file).

This bug also demonstrates that our basic readline implementation behaves differently than the others, in that it doesn't echo input that it receives from a script. I briefly thought about this, but decided not to fix this aspect of the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.