stripping extranneous junk out of vxWorks IOCs

["Jeff Hill" <johill@lanl.gov>]

Should the release notes for R3.14 state that a site can get additional
memory for their memory limited vxWorks IOCs by not loading the vxWorks
symbol table and the iocCore symbol table into the target? Instead they
could link EPICS with vxWorks on the workstation and then not load the
symbol table into the IOC. This approach will be very similar to how
iocCore is run on the host so I suppose that a person might discuss that
this could be the default vxWorks configuration with R3.14 in order to
reduce additional operating modes and the EPICS learning curve. This
will of course require debugging remotely with the Tornado host based
shell and the Tornado source level debugger. 

When we omit the symbol table the target shell becomes less useful if we
don't force a limited set of EPICS symbols to be loaded. We could, I
assume, use the iocsh to run the startup script, and use the host based
shell for diagnostics. It might also be nice to come up with an
attachment between iocsh and the vxWorks telnet server library so that
Tornado tools are not required to look into a normally functioning IOC
remotely.

The bottom line is that I can easily imagine that users with memory
limited vxWorks IOCs will be asking about this and therefore it might be
useful for someone to experiment enough so that we can decide if we
should support this in some way in makeBaseApp.pl.

Jeff
__________________________________________________________
Jeff Hill                     Internet     johill@lanl.gov
LANL MS H820                  Voice        505 665 1831
Los Alamos NM 87545 USA       FAX          505 665 5107