logging: Increase log processing stack size when NO_OPTIMIZATIONS
When optimizations are disabled more RAM is used and we get a stack
overflow on CONFIG_LOG_PROCESS_THREAD_STACK_SIZE. To rectify this,
increase the stack size when CONFIG_NO_OPTIMIZATIONS.
This does not scale well, and will have to be replaced by a a more
general solution eventually, but in the mean time it follows the
existing best practice established by the GCOV infrastructure in
commit e908ea9aa5
Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
This commit is contained in:
parent
7644d02598
commit
d5afe27207
1 changed files with 1 additions and 0 deletions
|
@ -264,6 +264,7 @@ config LOG_PROCESS_THREAD_SLEEP_MS
|
|||
config LOG_PROCESS_THREAD_STACK_SIZE
|
||||
int "Stack size for the internal log processing thread"
|
||||
default 2048 if COVERAGE_GCOV
|
||||
default 1024 if NO_OPTIMIZATIONS
|
||||
default 768
|
||||
help
|
||||
Set the internal stack size for log processing thread.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue