For those interested the callstack looks like this;

bsp_fatal_extension() at bspclean.c:32 0x700d42ba
_User_extensions_Iterate() at userextiterate.c:175 0x700ef42a
_User_extensions_Fatal() at userextimpl.h:307 0x700eb9b2
_Terminate() at interr.c:35 0x700eb9b2
_Internal_error() at interr.c:52 0x700eb9e2
_Thread_Do_dispatch() at threaddispatch.c:186 0x700edd0a
_Thread_Dispatch_enable() at threaddispatch.h:227 0x700ef0f8
_Thread_Change_life() at threadrestart.c:684 0x700ef0f8
_Thread_Set_life_protection() at threadrestart.c:691 0x700ef10c
_API_Mutex_Lock() at apimutexlock.c:29 0x700eae86
_RTEMS_Lock_allocator() at allocatormutex.c:26 0x700eae6a
_Region_Get_and_lock() at regionimpl.h:76 0x700e9cdc
rtems_region_get_segment() at regiongetsegment.c:68 0x700e9cdc
... some of my code ...
_Thread_Handler() at threadhandler.c:134 0x700edde2
_Thread_Get() at threadget.c:38 0x700edda8

Its not clear to me what the issue might be.

On 19 February 2018 at 13:13, Matthew J Fletcher <> wrote:

> All,
> Replying to my own post, with CPU_ENABLE_ROBUST_THREAD_DISPATCH set FALSE
> i get a fatal exception, this on a Cortex-M7, rtems 5.0.0 from git.
> I think i will have to work around the new behavior somehow.
> --
> regards
> ---
> Matthew J Fletcher


Matthew J Fletcher
users mailing list

Reply via email to