On 2014-02-21 12:01, Peter Dufault wrote:
On Feb 21, 2014, at 05:35 , Sebastian Huber
<sebastian.hu...@embedded-brains.de> wrote:
On 2014-02-21 11:31, Peter Dufault wrote:
On Feb 21, 2014, at 05:17 , Sebastian Huber<sebastian.hu...@embedded-brains.de>
wrote:
The preempt task is supposed to delete itself, but it cannot do this action
since it blocks on the puts(). Now the main thread continues and fails due to
the not deleted preempt task.
One workaround for this is to disable interrupt driven console output.
Is there a POSIXly correct way to wait for I/O to drain in a single thread?
I am not aware of a bullet proof solution. This issue is on my list for
several years now, but it never had a high enough priority.
I forgot to ask the important question: What happens when you increase the
number of tasks to e.g. 8? SP02 still didn't run, when I broke in with the
debugger it was always in the idle task.
It is the same problem: blocking on output. As a quick hack you can add
CPU_CFLAGS += -DTESTS_USE_PRINTK
to the *.cfg file of your BSP.
--
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.
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel