mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-02 01:13:26 +00:00
e0ca403f4c
k_thread_create() works as expected on both uninitialized memory, or threads that have completely exited. However, horrible and difficult to comprehend things can happen if a thread object is already being used by the kernel and k_thread_create() is called on it. Historically this has been a problem with test cases trying to be parsimonious with thread objects and not properly cleaning up after themselves. Add an assertion for this which should catch both the illegal creation of a thread already active, or threads racing to create the same thread object. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> |
||
|---|---|---|
| .. | ||
| include | ||
| atomic_c.c | ||
| cache_handlers.c | ||
| CMakeLists.txt | ||
| compiler_stack_protect.c | ||
| device.c | ||
| errno.c | ||
| fatal.c | ||
| futex.c | ||
| idle.c | ||
| init.c | ||
| Kconfig | ||
| kheap.c | ||
| mailbox.c | ||
| mem_domain.c | ||
| mem_slab.c | ||
| mempool_sys.c | ||
| mempool.c | ||
| mmu.c | ||
| msg_q.c | ||
| mutex.c | ||
| pipes.c | ||
| poll.c | ||
| queue.c | ||
| sched.c | ||
| sem.c | ||
| smp.c | ||
| stack.c | ||
| system_work_q.c | ||
| thread_abort.c | ||
| thread.c | ||
| timeout.c | ||
| timer.c | ||
| userspace_handler.c | ||
| userspace.c | ||
| version.c | ||
| work_q.c | ||