are removed, then the signal is masked also in the main(), and as
a result the POSIX version works.
The question I have is if the behavior in Xenomai (that is, not failing
like the POSIX counterpart) is correct or not...
bye
Paolo
--
Evidence S.R.L. - Paolo Gai, CEO
http://www.evidence.eu.com
Gilles Chanteperdrix wrote:
Paolo Gai wrote:
Gilles Chanteperdrix wrote:
Working around this issue means using calls to unlocked versions of libc
functions protected with Xenomai POSIX mutexes, such as, for example,
myputs and myputchar (sufficient for Paolo example) defined
or the
* SCHED_RR scheduler
*
* Copyright (C) 2002 by Paolo Gai
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later
Dear all,
First of all, I would like to thank Philippe for the long and exaustive
reply to my previous post about the scheduling example.
I'm now trying the POSIX skin to write a very simple example using
real-time priorities, RR and FIFO scheduling.
The idea is that a high priority task
Dear Gilles,
Thanks again for the answer...
Gilles Chanteperdrix wrote:
[...]
What happens for certain is that the access to stdout buffer, when
compiling with the -D_REENTRANT flag, is serialized with a GNU libc
POSIX mutex. This account for the consistent behaviour between GNU libc
Dear Gilles,
Thanks again for the answer...
Gilles Chanteperdrix wrote:
[...]
What happens for certain is that the access to stdout buffer, when
compiling with the -D_REENTRANT flag, is serialized with a GNU libc
POSIX mutex. This account for the consistent behaviour between GNU libc
(it's in secondary mode), and maybe
about L (if it has been created by UVMs). The Linux scheduler will
choose H, and H will be scheduled.
Is that right?
bye
Paolo Gai
http://www.evidence.eu.com
