summaryrefslogtreecommitdiff
path: root/src/Kconfig
diff options
context:
space:
mode:
authorMeco Jianting Man <[email protected]>2021-03-17 02:32:02 +0800
committerGitHub <[email protected]>2021-03-17 02:32:02 +0800
commit295b95cd7529bc9b85b4fb8ee8b37c62811ffbc8 (patch)
treeb834c7a930dd12735759a6358ccef2bb94cfcc6f /src/Kconfig
parentc3ffe18688a3696a486855ae98002714546bd836 (diff)
parentb12615f344e7e0824ab262994f443c452be04973 (diff)
Merge pull request #28 from RT-Thread/master
pr
Diffstat (limited to 'src/Kconfig')
-rw-r--r--src/Kconfig26
1 files changed, 12 insertions, 14 deletions
diff --git a/src/Kconfig b/src/Kconfig
index 803c827e51..aa8e514e5c 100644
--- a/src/Kconfig
+++ b/src/Kconfig
@@ -284,21 +284,19 @@ menu "Memory Management"
endchoice
- if RT_USING_SMALL_MEM
- config RT_USING_MEMTRACE
- bool "Enable memory trace"
- default n
- help
- When enable RT_USING_MEMTRACE with shell, developer can call cmd:
- 1. memtrace
- to dump memory block information.
- 2. memcheck
- to check memory block to avoid memory overwritten.
+ config RT_USING_MEMTRACE
+ bool "Enable memory trace"
+ default n
+ help
+ When enable RT_USING_MEMTRACE with shell, developer can call cmd:
+ 1. memtrace
+ to dump memory block information.
+ 2. memcheck
+ to check memory block to avoid memory overwritten.
- And developer also can call memcheck() in each of scheduling
- to check memory block to find which thread has wrongly modified
- memory.
- endif
+ And developer also can call memcheck() in each of scheduling
+ to check memory block to find which thread has wrongly modified
+ memory.
config RT_USING_HEAP
bool