Am 24.06.19 um 03:49 schrieb kevin james:
> I have a question concerning the EPICS SNL Stack Size. What information can
> be used to determine if the small default stack size isn't sufficient?
>
> What would be a sign that the large stack size should be set?
Hi Kevin
I took the freedom to forward your question to the EPICS tech-talk
mailing list; this question must be considered in a wider context of how
threads behave on your particular system.
Generally I'd say that stack consumption is related to two factors: the
nesting depths of function calls; and whether you allocate large blocks
of data on the stack i.e. as local variables. The former is usually only
a problem if you use recursion. The latter may become a problem
depending on
The sequencer's runtime system runs with a small and constant stack
usage. Any extra requirements would come either from C functions you
call from SNL, or from declaring /very/ large local variables (e.g.
inside an action block).
An indication that your stack is too small would be that your program or
sequencer thread crashes. This depends very much on the OS and architecture.
Cheers
Ben
Attachment:
signature.asc
Description: OpenPGP digital signature
- Navigate by Date:
- Prev:
Re: Empty string as SNL macro Benjamin Franksen via Tech-talk
- Next:
Re: EPICS Docker Container Florian Feldbauer via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Empty string as SNL macro Benjamin Franksen via Tech-talk
- Next:
AreaDetector ADAndor: Scan hangs because Acquire="Collecting" when acquisition finished (DetectorState_RBV='idle') David Vine via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|