You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by GitBox <gi...@apache.org> on 2020/09/14 13:49:06 UTC

[GitHub] [incubator-nuttx] davids5 commented on issue #1769: All arch need colorize the idle thread stack correctly

davids5 commented on issue #1769:
URL: https://github.com/apache/incubator-nuttx/issues/1769#issuecomment-692064922


   @xiaoxiang781216 I want to be sure:
   
   1)  I understand what you atr asking me to do here.
   2) both understand why  CONFIG_STACK_COLORATION was added in the first place. in 2013-11-01 10:16:5 b8085906b9db4cbb05977ed96105a473a0836eb1 
   
   Here is my understanding:
   
   1) The feature to color the stack is a **debugging feature**. It is enabled with CONFIG_STACK_COLORATION
   2) If CONFIG_STACK_COLORATION is enabled the <ARCH>_checkstack will be included in the build.
   3) hardfaults will dump stack usage
   4) proc file system will provide the stack used amount.
   5) Debug application can used this information to monitor the stack penetration.
   
   What do you mean by "your approach." ?
   
   Are you asking me to add the assembly based coloring to all the archs and chips defined in nuttx?
    
   If this is because of the TLS changes:  https://github.com/apache/incubator-nuttx/issues/986 
   
   Do we now have a debugging ONLY feature that the TLS is dependent on?
   


----------------------------------------------------------------
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:
users@infra.apache.org