michaelh/zephyr
1
0
Fork 0
Code Releases Activity

debug: remove !OMIT_FRAME_POINTER from EXCEPTION_STACK_TRACE

Browse source 
Not all stack trace implementation requires frame pointer, move
that dependency to architecture Kconfig.

Signed-off-by: Yong Cong Sin <ycsin@meta.com>
This commit is contained in:
Yong Cong Sin 2024-05-25 12:43:15 +08:00 • committed by Carles Cufí
commit 8a5823b474
4 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

1
arch/x86/core/Kconfig.ia32
View file

@ -168,6 +168,7 @@ config X86_EXCEPTION_STACK_TRACE
default y
depends on EXCEPTION_STACK_TRACE
depends on DEBUG_INFO
depends on !OMIT_FRAME_POINTER
help
Internal config to enable runtime stack traces on fatal exceptions.

1
arch/x86/core/Kconfig.intel64
View file

@ -34,6 +34,7 @@ config X86_EXCEPTION_STACK_TRACE
default y
depends on EXCEPTION_STACK_TRACE
depends on DEBUG_INFO
depends on !OMIT_FRAME_POINTER
depends on NO_OPTIMIZATIONS
help
Internal config to enable runtime stack traces on fatal exceptions.

1
subsys/debug/Kconfig
View file

@ -382,7 +382,6 @@ config SYMTAB
config EXCEPTION_STACK_TRACE
bool "Attempt to print stack traces upon exceptions"
default y
depends on !OMIT_FRAME_POINTER
help
If the architecture fatal handling code supports it, attempt to
print a stack trace of function memory addresses when an

1
tests/arch/common/stack_unwind/testcase.yaml
View file

@ -33,6 +33,7 @@ tests:
extra_configs:
- CONFIG_NO_OPTIMIZATIONS=y
- CONFIG_DEBUG_INFO=y
- CONFIG_OMIT_FRAME_POINTER=n
integration_platforms:
- qemu_x86
- qemu_x86_64