On 11/10/2018 15:37, Catalin Demergian wrote:
Hi,
Yes, there is a call to rtems_task_wake_after in the code; but in that
case state should have been STATES_DELAYING, right ?
The
state = 0x0 = STATES_READY
Wait.flags = 0x02 = THREAD_WAIT_STATE_BLOCKED
looks suspicious. It should be
state = 0x0 = STATES_READY
Wait.flags = 0x04 = THREAD_WAIT_STATE_READY_AGAIN
after a call to _Thread_Timeout(),
At another run, I got
state = 0x0 = STATES_READY
Wait.flags = 0x104 = THREAD_WAIT_CLASS_EVENT |
THREAD_WAIT_STATE_READY_AGAIN
Why would the state be ready in _Event_Seize ? could that value be
corrupt ?
I tried with the stack checker as well, but I didn't see any out of
band values.
Ok, good.
I still think it would be worth to try the latest RTEMS master just to
make sure we don't search a bug which is already fixed. Also RTEMS 5 as
more assertions in the debug configuration.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
