You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
At random the test case will segfault just after passing in the POSIX architecture
(could only reproduce (easily) when compiling with COVERAGE enabled)
The issue is caused by the Zephyr POSIX sleep.c not being compiled with the posix_cheats.h defines.
When the POSIX arch attempted to call the host sleep(), instead the Zephyr POSIX API replacement sleep() was called, which messed up the threads state.
In 8dc69e0 (zephyrproject-rtos#10280)
the POSIX API main kconfig option was replaced from
PTHREAD_IPC to POSIX_API.
But the posix_cheats.h header was left using the old option.
This means that some applications/tests which were not
selecting the PTHREAD_IPC API, but using some other Zephyr
POSIX compatible APIs could have trouble when compiled for the
POSIX architecture.
Fixeszephyrproject-rtos#13011
Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
In 8dc69e0 (#10280)
the POSIX API main kconfig option was replaced from
PTHREAD_IPC to POSIX_API.
But the posix_cheats.h header was left using the old option.
This means that some applications/tests which were not
selecting the PTHREAD_IPC API, but using some other Zephyr
POSIX compatible APIs could have trouble when compiled for the
POSIX architecture.
Fixes#13011
Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
Describe the bug
At random the test case will segfault just after passing in the POSIX architecture
(could only reproduce (easily) when compiling with COVERAGE enabled)
The issue is caused by the Zephyr POSIX sleep.c not being compiled with the posix_cheats.h defines.
When the POSIX arch attempted to call the host
sleep()
, instead the Zephyr POSIX API replacement sleep() was called, which messed up the threads state.To Reproduce
Steps to reproduce the behavior:
Expected behavior
No segfault
Impact
Intermitent segfault after the case pases => confused users (the likelyhood is not too high, so the 3 retries in CI were hiding it)
Environment (please complete the following information):
Additional context
Bugfix incoming
The text was updated successfully, but these errors were encountered: