As a follow-up from the discussions here:
https://lists.rtems.org/pipermail/users/2021-June/068454.html
For RTEMS5 I noticed that an assertion fails for the Zedboard BSP if RTEMS is
compiled with the --enable-debug option.
The assert seems to be triggered during the execution of rtems_bsd_initialize
in the init task. The backtrace looks like this:
Breakpoint 4, _Terminate (the_source=RTEMS_FATAL_SOURCE_ASSERT,
the_error=3378872)
at ../../../../../c/src/../../cpukit/score/src/interr.c:36
36 _User_extensions_Fatal( the_source, the_error );
(gdb) bt
#0 _Terminate (the_source=RTEMS_FATAL_SOURCE_ASSERT, the_error=3378872)
at ../../../../../c/src/../../cpukit/score/src/interr.c:36
#1 0x0010aa26 in rtems_fatal (fatal_source=RTEMS_FATAL_SOURCE_ASSERT,
error_code=3378872)
at /workspace/rtems/cpukit/include/rtems/fatal.h:88
#2 0x0010aa98 in __assert_func (
file=0x20d250 "/workspace/rtems/cpukit/include/rtems/score/chainimpl.h",
line=688,
func=0x20d2a4 <__func__.5956> "_Chain_Append_unprotected",
failedexpr=0x20d228 "_Chain_Is_node_off_chain( the_node )")
at ../../../../../c/src/../../cpukit/libcsupport/src/__assert.c:52
#3 0x0011be6c in _Chain_Append_unprotected (the_chain=0x3126d4
<_Configuration_Scheduler_priority_dflt+1236>,
the_node=0x310d48 <_RTEMS_tasks_Objects+4160>)
at /workspace/rtems/cpukit/include/rtems/score/chainimpl.h:688
#4 0x0011c1ca in _Scheduler_priority_Ready_queue_enqueue (node=0x310d48
<_RTEMS_tasks_Objects+4160>,
ready_queue=0x310f28 <_RTEMS_tasks_Objects+4640>, bit_map=0x312200
<_Configuration_Scheduler_priority_dflt>)
at /workspace/rtems/cpukit/include/rtems/score/schedulerpriorityimpl.h:119
#5 0x0011c276 in _Scheduler_priority_Unblock (scheduler=0x2089f0
<_Scheduler_Table>,
the_thread=0x310d48 <_RTEMS_tasks_Objects+4160>, node=0x310ef0
<_RTEMS_tasks_Objects+4584>)
at ../../../../../c/src/../../cpukit/score/src/schedulerpriorityunblock.c:50
#6 0x0011d83a in _Scheduler_Unblock (the_thread=0x310d48
<_RTEMS_tasks_Objects+4160>)
at /workspace/rtems/cpukit/include/rtems/score/schedulerimpl.h:322
#7 0x0011d8d8 in _Thread_Clear_state_locked (the_thread=0x310d48
<_RTEMS_tasks_Objects+4160>, state=4294967295)
at ../../../../../c/src/../../cpukit/score/src/threadclearstate.c:44
#8 0x00120230 in _Thread_Start (the_thread=0x310d48
<_RTEMS_tasks_Objects+4160>, entry=0x338fa4,
lock_context=0x338fa0) at
../../../../../c/src/../../cpukit/score/src/threadstart.c:43
#9 0x001171ac in rtems_task_start (id=167837701, entry_point=0x190f65
<taskqueue_thread_loop>, argument=3282804)
at ../../../../../c/src/../../cpukit/rtems/src/taskstart.c:56
#10 0x001875f4 in rtems_bsd_threads_init_late (arg=<optimized out>) at
../../rtemsbsd/rtems/rtems-kernel-thread.c:211
#11 0x0018cf58 in _bsd_mi_startup () at ../../freebsd/sys/kern/init_main.c:327
#12 0x001865e0 in rtems_bsd_initialize () at
../../rtemsbsd/rtems/rtems-kernel-init.c:150
#13 0x001058e2 in register_network_devices (ip=ip@entry=0x31fe24 <ret>
"10.42.0.225")
at
/localdata2/somm_ja/hap/fcc-software/sw/common/rtems/register_ethernet.cpp:130
#14 0x0010534c in task_system_init () at main.cpp:59
#15 0x00120270 in _Thread_Entry_adaptor_numeric (executing=0x30fd08
<_RTEMS_tasks_Objects>)
at
../../../../../c/src/../../cpukit/score/src/threadentryadaptornumeric.c:25
#16 0x0011e204 in _Thread_Handler () at
../../../../../c/src/../../cpukit/score/src/threadhandler.c:139
#17 0x00128e48 in _Thread_Start_multitasking ()
at ../../../../../c/src/../../cpukit/score/src/threadstartmultitasking.c:64
Best regards,
Jan
Deutsches Zentrum für Luft- und Raumfahrt e. V. (DLR)
German Aerospace Center
Institute for Software Technology | Software for Space Systems and Interactive
Visualization | Lilienthalplatz 7 | 38108 Braunschweig | Germany
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
