Philippe Gerum wrote:
Gilles Chanteperdrix wrote:
Niklaus Giger wrote:
> Do you have any ideas? Thanks in advance.
No idea, the x86 version does not seem to have the same problem, but
valgrind give many errors.
Valgrind chokes on the co-routine switching code, which is fair enough,
since it's quite hard for it to track stack context changes the way
setcontext/getcontext do it.
However, like for the previous stack size issue with satch.c, I wonder
if the fixed-size stacks allocated by the simulator for its threads are
Does this patch make the situation any better?
--- sim/vm/thread.cc (revision 1083)
+++ sim/vm/thread.cc (working copy)
@@ -900,7 +900,7 @@
const char *_name) :
tcbarg = _tcbarg;
faddr = _faddr;
Xenomai-core mailing list