Re: [Xenomai-core] Errors running sim testsuite for vxWorks

[Philippe Gerum <rpm@xenomai.org>]

Philippe Gerum wrote:
> 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 not overflowed.
>>
> 
> Does this patch make the situation any better?
> 
> --- sim/vm/thread.cc    (revision 1083)
> +++ sim/vm/thread.cc    (working copy)
> @@ -900,7 +900,7 @@
>              void *_faddr,
>              int _pflags,
>              const char *_name) :
> -    MvmThread(_name,_pflags|MVM_THREAD_CLIENT,16384)
> +    MvmThread(_name,_pflags|MVM_THREAD_CLIENT,32768)
>  {
>      tcbarg = _tcbarg;
>      faddr = _faddr;
>

This one is better:

--- sim/vm/thread.cc	(revision 1083)
+++ sim/vm/thread.cc	(working copy)
@@ -900,7 +900,7 @@
  			void *_faddr,
  			int _pflags,
  			const char *_name) :
-    MvmThread(_name,_pflags|MVM_THREAD_CLIENT,16384)
+    MvmThread(_name,_pflags|MVM_THREAD_CLIENT,32768)
  {
      tcbarg = _tcbarg;
      faddr = _faddr;
@@ -915,7 +915,7 @@
  }

  XenoThread::XenoThread (const char *_name) :
-    MvmThread(_name,MVM_IFACE_HIDDEN,16384)
+    MvmThread(_name,MVM_IFACE_HIDDEN,32768)
  {
      tcbarg = NULL;
      faddr = NULL;

-- 

Philippe.