diff options
| author | Grissiom <[email protected]> | 2013-10-11 22:46:05 +0800 |
|---|---|---|
| committer | Grissiom <[email protected]> | 2013-10-11 22:51:38 +0800 |
| commit | 6f71308ef529bfcecd54daaa309d1336ef0c6366 (patch) | |
| tree | c21fe47733df26afc267dbcf5c19f9e7c1f5fcc7 /include | |
| parent | 786a5541a3cdcc419c349943ee717f680cb87ec8 (diff) | |
kernel: add RT_DEBUG_IN_THREAD_CONTEXT
In thread context means: 1) the scheduler has been started; 2) not in
interrupt context. It is more stronger than RT_DEBUG_NOT_IN_INTERRUPT.
With this commit, you will catch the error on situations like taking
mutex before scheduling instead of crashing on NULL pointer reference.
Diffstat (limited to 'include')
| -rw-r--r-- | include/rtdebug.h | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/include/rtdebug.h b/include/rtdebug.h index ebf85d6dba..5172778578 100644 --- a/include/rtdebug.h +++ b/include/rtdebug.h @@ -103,8 +103,29 @@ do \ rt_hw_interrupt_enable(level); \ } \ while (0) + +/* "In thread context" means: + * 1) the scheduler has been started + * 2) not in interrupt context. + */ +#define RT_DEBUG_IN_THREAD_CONTEXT \ +do \ +{ \ + rt_base_t level; \ + level = rt_hw_interrupt_disable(); \ + if (rt_thread_self() == RT_NULL) \ + { \ + rt_kprintf("Function[%s] shall not be used before scheduler start\n", \ + __FUNCTION__); \ + RT_ASSERT(0) \ + } \ + RT_DEBUG_NOT_IN_INTERRUPT; \ + rt_hw_interrupt_enable(level); \ +} \ +while (0) #else #define RT_DEBUG_NOT_IN_INTERRUPT +#define RT_DEBUG_IN_THREAD_CONTEXT #endif #else /* RT_DEBUG */ |