The ipToAsciiProxy thread calls upon vendor libraries which may use significant amounts of stack. Account for this by providing the thread with an epicsThreadStackBig stack.

This commit is contained in:
W. Eric Norum
2008-07-21 17:40:44 +00:00
parent 72090c2e32
commit 02b87df99c
2 changed files with 5 additions and 1 deletions

View File

@@ -30,6 +30,10 @@ either <tt>iocInit</tt> or <tt>iocBuild</tt> + <tt>iocRun</tt>) the
stopping all scan activity. The <tt>iocRun</tt> command restarts the IOC from
this state.</p>
<h4>ipToAsciiProxy</h4>
<p>This thread calls upon vendor libraries which may use significant amounts of stack. Account for this by providing the ipToAsciiProxy thread with an epicsThreadStackBig stack.</p>
<p>While this might seem like a useful thing to be able to do, we have not
tested it on IOCs using real-world I/O, and it is not unlikely that pausing an
operational IOC could cause irremdial havok to any device support, sequence

View File

@@ -164,7 +164,7 @@ ipAddrToAsciiEngine & ipAddrToAsciiEngine::allocate ()
ipAddrToAsciiEnginePrivate::ipAddrToAsciiEnginePrivate () :
thread ( *this, "ipToAsciiProxy",
epicsThreadGetStackSize(epicsThreadStackSmall),
epicsThreadGetStackSize(epicsThreadStackBig),
epicsThreadPriorityLow ),
pCurrent ( 0 ), cancelPendingCount ( 0u ), exitFlag ( false ),
callbackInProgress ( false )