-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sanitycheck --coverage: stack overflows on qemu_x86, mps2_an385 and qemu_x86_nommu #15206
Labels
Comments
cinlyooi-intel
changed the title
sanitycheck --coverage: stack overflows on qemu_x86 and mps2_an385
sanitycheck --coverage: stack overflows on qemu_x86, mps2_an385 and qemu_x86_nommu
Apr 5, 2019
wentongwu
added a commit
to wentongwu/zephyr
that referenced
this issue
Apr 9, 2019
for SDK 0.10.0, it consumes more stack size when coverage enabled, so adjust stack size to fix stack overflow issue. Fixes: zephyrproject-rtos#15206. Signed-off-by: Wentong Wu <[email protected]>
wentongwu
added a commit
to wentongwu/zephyr
that referenced
this issue
Apr 9, 2019
for SDK 0.10.0, it consumes more stack size when coverage enabled, so adjust stack size to fix stack overflow issue. Fixes: zephyrproject-rtos#15206. Signed-off-by: Wentong Wu <[email protected]>
nashif
pushed a commit
that referenced
this issue
Apr 11, 2019
for SDK 0.10.0, it consumes more stack size when coverage enabled, so adjust stack size to fix stack overflow issue. Fixes: #15206. Signed-off-by: Wentong Wu <[email protected]>
nashif
pushed a commit
that referenced
this issue
Apr 11, 2019
for SDK 0.10.0, it consumes more stack size when coverage enabled, so adjust stack size to fix stack overflow issue. Fixes: #15206. Signed-off-by: Wentong Wu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
Closure of bug #14500 via pull request #15005 remove the majority of coverage error. (Thank you for the effort. I appreciate it a lot)
I am trying not to look a gift horse in the mouth, but here are the remaining errors after merging #15005.
To Reproduce
It is confirmed that, if I am not running code coverage, i.e.
all the test that failed in coverage tests, passed here.
Environment (please complete the following information):
** Failures **
For:
see: sanity-out/mps2_an385/tests/kernel/fatal/kernel.common.stack_sentinel/run.log
see: sanity-out/mps2_an385/tests/kernel/mem_protect/mem_protect/kernel.memory_protection/run.log
see: sanity-out/mps2_an385/tests/kernel/arm_irq_vector_table/arch.interrupt/handler.log
see: sanity-out/mps2_an385/tests/kernel/mem_protect/mem_protect/kernel.memory_protection/run.log
see: sanity-out/mps2_an385/tests/kernel/lifo/lifo_usage/kernel.lifo.usage/handler.log
see: sanity-out/mps2_an385/tests/kernel/mem_pool/mem_pool_api/kernel.memory_pool/handler.log
see: sanity-out/mps2_an385/tests/kernel/mem_protect/stackprot/kernel.memory_protection/handler.log
see: sanity-out/mps2_an385/tests/kernel/mem_protect/userspace/kernel.memory_protection.userspace/handler.log
No output in handler.log
see: sanity-out/mps2_an385/tests/kernel/mutex/sys_mutex/kernel.mutex/handler.log
This one has GCOV data.
see: sanity-out/mps2_an385/tests/kernel/pipe/pipe/kernel.pipe/handler.log
This one has GCOV data
see: sanity-out/mps2_an385/tests/kernel/profiling/profiling_api/kernel.profiling/handler.log
see: sanity-out/mps2_an385/tests/kernel/timer/timer_api/kernel.timer/handler.log
This one has GCOV data
see: sanity-out/mps2_an385/tests/kernel/threads/thread_apis/kernel.threads/handler.log
68/214 mps2_an385 tests/subsys/logging/log_core/logging.log_core PASSED
see: sanity-out/qemu_x86/tests/kernel/mem_pool/mem_pool_api/kernel.memory_pool/run.log
see: sanity-out/qemu_x86/tests/kernel/mem_protect/stackprot/kernel.memory_protection/run.log
see: sanity-out/qemu_x86/tests/kernel/pipe/pipe/kernel.pipe/handler.log
see: sanity-out/qemu_x86_nommu/tests/kernel/mem_protect/stackprot/kernel.memory_protection/run.log
179/214 qemu_x86_nommu tests/kernel/mutex/sys_mutex/kernel.mutex FAILED: failed
see: sanity-out/qemu_x86_nommu/tests/kernel/mutex/sys_mutex/kernel.mutex/handler.log
214/214 qemu_x86_nommu tests/kernel/threads/thread_init/kernel.threads FAILED: timeout
see: sanity-out/qemu_x86_nommu/tests/kernel/threads/thread_init/kernel.threads/handler.log
The text was updated successfully, but these errors were encountered: