Hello,
in pSOS skin function ev_receive() in file event.c I've found a bug.
When ev_receive() is called with EV_WAIT and an event is received, the
task is unblocked and everything is okay, then in this case the copy of the
actual received events into *events_r is missing.
Regards
Markus
On Wed, 2007-02-07 at 11:36 +0100, Markus Osterried wrote:
Hello,
in pSOS skin function ev_receive() in file event.c I've found a bug.
When ev_receive() is called with EV_WAIT and an event is received, the
task is unblocked and everything is okay, then in this case the copy of the
actual
On Wed, 2007-02-07 at 11:57 +0100, Philippe Gerum wrote:
On Wed, 2007-02-07 at 11:36 +0100, Markus Osterried wrote:
Hello,
in pSOS skin function ev_receive() in file event.c I've found a bug.
When ev_receive() is called with EV_WAIT and an event is received, the
task is unblocked and
In timeout case events_r is don't care.
When using pSOS skin in user space, __ev_receive() in syscall.c copy
events_r to user space only when ev_receive was successful.
But this comply with pSOS manual: If successful, ev_receive() returns the
actual events captured by the call in the
location
On Wed, 2007-02-07 at 12:51 +0100, Markus Osterried wrote:
In timeout case events_r is don't care.
I would swear having seen a copy back being documented in the timeout
case in some oldish pSOS 2.3 manual a looong time ago, but since I don't
have it at hand anymore, maybe it's just -ENOBRAIN on
Is there a way to launch my realtime task from another linux program
using system() C call ?
I have tried it , but when system call dies my rt task dies too ...
any idea ?
steph
___
Xenomai-core mailing list
Xenomai-core@gna.org
On Tue, 2007-02-06 at 07:47 +0100, Niklaus Giger wrote:
Hi
After spending a week skiing I discovered that I had to update the buildbot
to
use the 2.6.19 kernels everywhere. Seems to work.
I also found that since February 2 I get the following error message
g++ -DHAVE_CONFIG_H -I.
Stéphane ANCELOT wrote:
Is there a way to launch my realtime task from another linux program
using system() C call ?
I have tried it , but when system call dies my rt task dies too ...
any idea ?
Why does the system call die ? Do you observe the same behaviour with
non xenomai applications
Hi all,
fiddling with latest Xenomai trunk and 2.3.x on one of our robots (there
is still a bug in trunk /wrt broken timeouts of rt_dev_read on
xeno_16550A - different issue...), I ran into a weird behaviour of
rtcanrecv:
I have a continuous stream of a few thousand packets/s towards the
robot.
Jan Kiszka wrote:
Hi all,
fiddling with latest Xenomai trunk and 2.3.x on one of our robots (there
is still a bug in trunk /wrt broken timeouts of rt_dev_read on
xeno_16550A - different issue...), I ran into a weird behaviour of
rtcanrecv:
I have a continuous stream of a few thousand
my linux user task uses a system() call in order to call a bash script
to restart the realtime task as follow :
user interface C call :
system(restart_task.sh);
give back hand to user interface
bash script restart_task.sh :
killall -15 mytask
sleep 2
mytask
system call dies because
11 matches
Mail list logo
