Hi,
due to bugs, it may happen that the latency test spots are due to
involuntary mode switches to secondary mode. This is bad, because users
testing xenomai quickly on their platform may find a bad latency, and go
quickly to conclusions without even posting a mail on the mailing lists.
When exiting a process, rtdk buffers are not flushed. Fix that by
introducing a destructor for the library which flushes the buffers.
When forking, if the main thread has an rt_printf buffer, it is reused by
the child, which is a good thing, however, it is not emptied, so could cause
the same
Those who accord, Say Hear, Hear, +1 or Me too, depending on their
geological or social situation.
+1
Me too
Hear, Hear
(an American in Austria)
___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core
Those who accord, Say Hear, Hear, +1 or Me too, depending on their
geological or social situation.
After intensive research and quiet contemplation, I believe that I know
the answer...
Me too!
Thanks for a great system. It's letting us do some nice astronomical
instruments and testbeds
