Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-10 Thread Sebastian Huber
On 10/10/2018 16:18, Catalin Demergian wrote: Hi, I got into another issue when I tried ping -f [/] # assertion "the_watchdog->state == WATCHDOG_ACTIVE" failed: file "../../../../../../c/src/../../cpukit/score/src/watchdogremove.c", line 34, function: _Watchdog_Remove_it *** PROFILING R

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-10 Thread Catalin Demergian
> > Hi, I got into another issue when I tried ping -f [/] # assertion "the_watchdog->state == WATCHDOG_ACTIVE" failed: file "../../../../../../c/src/../../cpukit/score/src/watchdogremove.c", line 34, function: _Watchdog_Remove_it *** PROFILING REPORT BEGIN PMC_APP *** 2 1

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-10 Thread Sebastian Huber
On 10/10/2018 14:27, Catalin Demergian wrote: I was debugging to follow what's going on with the state of the task in _Event_Seize and when trying to step over _Thread_Dispatch_enable( cpu_self ) call at the end of the function I got this in the debugger 0x80acf38->_Heap_Walk->_Heap_Walk_chec

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-10 Thread Catalin Demergian
Hi, we ran those tests and they all passed. I was debugging to follow what's going on with the state of the task in _Event_Seize and when trying to step over _Thread_Dispatch_enable( cpu_self ) call at the end of the function I got this in the debugger 0x80acf38->_Heap_Walk->_Heap_Walk_check_con