Fix two uses of DEBUG_COLORATION vs STACK_COLORATION (from David Sidrane). Also some corrected comments
This commit is contained in:
parent
edf876ed1a
commit
caf4a7ffc6
@ -6,10 +6,10 @@
|
||||
config SYSTEM_STACKMONITOR
|
||||
bool "Stack monitor"
|
||||
default n
|
||||
depends on DEBUG_COLORATION && !KERNEL_BUILD
|
||||
depends on STACK_COLORATION && !KERNEL_BUILD
|
||||
---help---
|
||||
If the stack coloration feature is enabled (DEBUG_COLORATION) this
|
||||
option will select the Stack Moitor. The stack monitor is a daemoni
|
||||
If the stack coloration feature is enabled (STACK_COLORATION) this
|
||||
option will select the Stack Monitor. The stack monitor is a daemon
|
||||
that will periodically assess stack usage by all tasks and threads
|
||||
in the system. This feature depends on internal OS features and,
|
||||
hence, is not available if the NuttX kernel build is selected.
|
||||
|
Loading…
x
Reference in New Issue
Block a user