Typo:
epicsThreadGetStackSize(-1) behaves like epicsThreadGetStackSize(2), not
like epicsThreadGetStackSize(0) as expected.
On 28.02.2018 15:48, Dirk Zimoch wrote:
Hi folks,
I just noticed that epicsThreadGetStackSize(-1) behaves like
epicsThreadGetStackSize(3), not like epicsThreadGetStackSize(1) as
expected.
In other words if the requested size is smaller than small, I get a big
stack, not a small one.
Is that the intended behavior or should I write a fix?
Other fixes are needed anyway: The error messages have no \n.
Also I would like to implement a way to configure the stack sizes
dynamically (e.g. using a iocsh variable), so that I do not need to
rebuild EPICS base for stack hungry applications or for applications
with so many clients that stack size becomes an issue (32bit embedded
Linux with >400 CA clients in my case).
Any interest?
I would implement this for 3.14.12, as this is what we still use here.
Dirk
- References:
- epicsThreadGetStackSize Dirk Zimoch
- Navigate by Date:
- Prev:
epicsThreadGetStackSize Dirk Zimoch
- Next:
Conversion from hex number string to LONG-type field Bruno Martins
- Index:
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:
epicsThreadGetStackSize Dirk Zimoch
- Next:
Conversion from hex number string to LONG-type field Bruno Martins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|