xiaoxiang781216 edited a comment on pull request #3471:
URL: https://github.com/apache/incubator-nuttx/pull/3471#issuecomment-817345061
sim IDLE thread stack is very specific because:
1. The stack isn't created by NuttX, but reused from host main thread stack,
which mean it will be dynamically extended by host OS as needed and then is
never overflow.
2. All pseudo device drivers(e.g. tty, tap, x11) talk to the host devices
inside the idle loop, which mean the stack consumption is much higher than the
epxectation.
3. sim still initialze IDLE thread stack info from
CONFIG_IDLETHREAD_STACKSIZE:
https://github.com/apache/incubator-nuttx/blob/master/arch/sim/src/sim/up_initialstate.c#L54-L60
So, from item 2 and 3, you will see the stack usage near or equals 100%
frequently, but the program still can run correctly due to item 1.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
