Re: scan task stack overflow

[Ralph Lange <Ralph.Lange@bessy.de>]

Laznovsky, Michael wrote:

> How about driving some of them with fanout records? 
> Only one scan per fanout then.
>
> Or an FLNK chain...
>  
Or pointing CPP input links back to fields ...
Or using the Event scan mechanism (together with an eventRecord) for 
groups of records that belong together...

In general, the different stack sizes for EPICS base tasks are hardcoded 
(see <BASE>/src/libCom/osi/os/<OS>/osdThread.c). There is the 
possibility to switch completely to using the OS's default stack size 
(by setting OSITHREAD_USE_DEFAULT_STACK = YES when compiling EPICS 
base), but you would have to increase the default stack size on your 
target to make it large enough, which then would be used for *all* 
tasks, not just the "big" ones. I don't know if your system could live 
with such a waste of memory.

Reorganizing your database in one of the mentioned ways is probably the 
most slim, elegant, and advisable solution.

Ralph