michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/tests/arch/common/stack_unwind/testcase.yaml

79 lines
1.9 KiB
YAML
Raw Normal View History

tests: arch: common: add stack_unwind test Added test for archs that support it. It triggers an exception and verify that the fatal message has stack unwind info. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-04-02 17:02:20 +08:00
common:
harness: console
ignore_faults: true
ignore_qemu_crash: true
tags: kernel
tests:
arch: riscv: Add support for stack unwind without fp Add a stack unwind implementation that only uses `sp` Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-13 15:55:24 +08:00
arch.common.stack_unwind.riscv_fp:
tests: arch: common: add stack_unwind test Added test for archs that support it. It triggers an exception and verify that the fatal message has stack unwind info. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-04-02 17:02:20 +08:00
arch_allow: riscv
integration_platforms:
tests: arch: common: stack_unwind: add qemu_riscv32e qemu_riscv32e uses a different ISA and is kinda special, add it to the testcase for better coverage. Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
2024-08-07 20:13:48 +08:00
- qemu_riscv32e
tests: arch: common: add stack_unwind test Added test for archs that support it. It triggers an exception and verify that the fatal message has stack unwind info. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-04-02 17:02:20 +08:00
- qemu_riscv32
- qemu_riscv64
arch: generalize frame pointer via CONFIG_FRAME_POINTER introduction Enabling `CONFIG_FRAME_POINTER` allows the users to build the kernel with frame-pointer. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-13 13:12:12 +08:00
extra_configs:
- CONFIG_FRAME_POINTER=y
tests: arch: common: add stack_unwind test Added test for archs that support it. It triggers an exception and verify that the fatal message has stack unwind info. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-04-02 17:02:20 +08:00
harness_config:
type: multi_line
regex:
- "E: call trace:"
arch: riscv: stacktrace: implement `arch_stack_walk()` Created the `arch_stack_walk()` function out from the original `z_riscv_unwind_stack()`, it's been updated to support unwinding any thread. Updated the stack_unwind test case accordingly. Increased the delay in `test_fatal_on_smp`, to wait for the the fatal thread to be terminated, as stacktrace can take a bit more time. Doubled the kernel/smp testcase timeout from 60 (default) to 120s, as some of the tests can take a little bit more than 60s to finish. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-31 21:24:54 +08:00
- "E: 0: ra: \\w+"
- "E: 1: ra: \\w+"
arch: riscv: Add support for stack unwind without fp Add a stack unwind implementation that only uses `sp` Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-13 15:55:24 +08:00
arch.common.stack_unwind.riscv_sp:
arch_allow: riscv
integration_platforms:
tests: arch: common: stack_unwind: add qemu_riscv32e qemu_riscv32e uses a different ISA and is kinda special, add it to the testcase for better coverage. Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
2024-08-07 20:13:48 +08:00
- qemu_riscv32e
arch: riscv: Add support for stack unwind without fp Add a stack unwind implementation that only uses `sp` Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-13 15:55:24 +08:00
- qemu_riscv32
- qemu_riscv64
harness_config:
type: multi_line
regex:
- "E: call trace:"
arch: riscv: stacktrace: implement `arch_stack_walk()` Created the `arch_stack_walk()` function out from the original `z_riscv_unwind_stack()`, it's been updated to support unwinding any thread. Updated the stack_unwind test case accordingly. Increased the delay in `test_fatal_on_smp`, to wait for the the fatal thread to be terminated, as stacktrace can take a bit more time. Doubled the kernel/smp testcase timeout from 60 (default) to 120s, as some of the tests can take a little bit more than 60s to finish. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-31 21:24:54 +08:00
- "E: 0: ra: \\w+"
- "E: 1: ra: \\w+"
tests: arch: common: add stack_unwind test Added test for archs that support it. It triggers an exception and verify that the fatal message has stack unwind info. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-04-02 17:02:20 +08:00
arch.common.stack_unwind.x86:
arch_allow: x86
extra_configs:
- CONFIG_NO_OPTIMIZATIONS=y
debug: remove `!OMIT_FRAME_POINTER` from EXCEPTION_STACK_TRACE Not all stack trace implementation requires frame pointer, move that dependency to architecture Kconfig. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-25 12:43:15 +08:00
- CONFIG_OMIT_FRAME_POINTER=n
tests: arch: common: add stack_unwind test Added test for archs that support it. It triggers an exception and verify that the fatal message has stack unwind info. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-04-02 17:02:20 +08:00
integration_platforms:
- qemu_x86
- qemu_x86_64
harness_config:
type: multi_line
regex:
- "E: call trace:"
arch: x86: implement `arch_stack_walk()` Currently it supports `esf` based unwinding only. Then, update the exception stack unwinding to use `arch_stack_walk()`, and update the Kconfigs & testcase accordingly. Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
2024-08-14 17:08:28 +08:00
- "E: 0: \\w+"
- "E: 1: \\w+"
tests: arch: common: stack_unwind: cleanup Kconfig Refactor to cleanup some Kconfigs that are not required by certain architectures to produce the traces. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-13 15:48:46 +08:00
arch.common.stack_unwind.arm64:
tests: arch: common: add stack_unwind test Added test for archs that support it. It triggers an exception and verify that the fatal message has stack unwind info. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-04-02 17:02:20 +08:00
arch_allow:
- arm64
integration_platforms:
- qemu_cortex_a53
arch: generalize frame pointer via CONFIG_FRAME_POINTER introduction Enabling `CONFIG_FRAME_POINTER` allows the users to build the kernel with frame-pointer. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-13 13:12:12 +08:00
extra_configs:
- CONFIG_FRAME_POINTER=y
tests: arch: common: add stack_unwind test Added test for archs that support it. It triggers an exception and verify that the fatal message has stack unwind info. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-04-02 17:02:20 +08:00
harness_config:
type: multi_line
regex:
- "E: backtrace 0: fp: \\w+ lr: \\w+"
- "E: backtrace 1: fp: \\w+ lr: \\w+"
arch: riscv: use symtab to print function name in stack trace Selecting `CONFIG_EXCEPTION_STACK_TRACE_SYMTAB` will enable the symtab generation which will be used in the stack trace to print the function name of the return address. Updated the `stack_unwind` test to test the symbols in a stack trace. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-18 16:49:42 +08:00
arch.common.stack_unwind.symtab:
arch_allow:
- riscv
arch: arm64: use symtab to print function name in stack trace Selecting `CONFIG_SYMTAB` will enable the symtab generation which will be used in the stack trace to print the function name of the return address. Added `arm64` to the `arch.common.stack_unwind.symtab` test. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-18 17:36:43 +08:00
- arm64
arch: riscv: use symtab to print function name in stack trace Selecting `CONFIG_EXCEPTION_STACK_TRACE_SYMTAB` will enable the symtab generation which will be used in the stack trace to print the function name of the return address. Updated the `stack_unwind` test to test the symbols in a stack trace. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-18 16:49:42 +08:00
integration_platforms:
tests: arch: common: stack_unwind: add qemu_riscv32e qemu_riscv32e uses a different ISA and is kinda special, add it to the testcase for better coverage. Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
2024-08-07 20:13:48 +08:00
- qemu_riscv32e
arch: riscv: use symtab to print function name in stack trace Selecting `CONFIG_EXCEPTION_STACK_TRACE_SYMTAB` will enable the symtab generation which will be used in the stack trace to print the function name of the return address. Updated the `stack_unwind` test to test the symbols in a stack trace. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-18 16:49:42 +08:00
- qemu_riscv32
- qemu_riscv64
arch: arm64: use symtab to print function name in stack trace Selecting `CONFIG_SYMTAB` will enable the symtab generation which will be used in the stack trace to print the function name of the return address. Added `arm64` to the `arch.common.stack_unwind.symtab` test. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-18 17:36:43 +08:00
- qemu_cortex_a53
arch: generalize frame pointer via CONFIG_FRAME_POINTER introduction Enabling `CONFIG_FRAME_POINTER` allows the users to build the kernel with frame-pointer. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-13 13:12:12 +08:00
extra_configs:
- CONFIG_FRAME_POINTER=y
tests: arch: common: stack_unwind: fix symtab test The symtab test should have the `CONFIG_EXCEPTION_STACK_TRACE_SYMTAB` enabled. This was not caught in the CI previously as the regex was also wrong, '[' and ']' are regex syntax and should be escaped. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-07-06 17:38:29 +08:00
- CONFIG_EXCEPTION_STACK_TRACE_SYMTAB=y
arch: riscv: use symtab to print function name in stack trace Selecting `CONFIG_EXCEPTION_STACK_TRACE_SYMTAB` will enable the symtab generation which will be used in the stack trace to print the function name of the return address. Updated the `stack_unwind` test to test the symbols in a stack trace. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-18 16:49:42 +08:00
harness_config:
type: multi_line
regex:
tests: arch: common: stack_unwind: fix symtab test The symtab test should have the `CONFIG_EXCEPTION_STACK_TRACE_SYMTAB` enabled. This was not caught in the CI previously as the regex was also wrong, '[' and ']' are regex syntax and should be escaped. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-07-06 17:38:29 +08:00
- "\\[func1\\+0x\\w+\\]"
- "\\[func2\\+0x\\w+\\]"
- "\\[func1\\+0x\\w+\\]"
- "\\[func2\\+0x\\w+\\]"
- "\\[func1\\+0x\\w+\\]"
Copy permalink