From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4464A68E.2000100@domain.hid>
Date: Fri, 12 May 2006 17:15:26 +0200
From: Philippe Gerum <rpm@xenomai.org>
MIME-Version: 1.0
Subject: Re: [Xenomai-core] Errors running sim testsuite for vxWorks
References: <200605111823.51650.niklaus.giger@domain.hid>	<17507.27519.455277.534105@domain.hid>	<200605111956.57892.niklaus.giger@domain.hid>	<17507.39938.328795.132737@domain.hid>	<4463C090.8050309@domain.hid>
	<4464A58A.9070401@domain.hid>
In-Reply-To: <4464A58A.9070401@domain.hid>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: "Xenomai life and development \(bug reports, patches,
	discussions\)" <xenomai.xenomai.org>
List-Unsubscribe: <https://mail.gna.org/listinfo/xenomai-core>,
	<mailto:xenomai-core-request@domain.hid>
List-Archive: </public/xenomai-core>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-core-request@domain.hid>
List-Subscribe: <https://mail.gna.org/listinfo/xenomai-core>,
	<mailto:xenomai-core-request@domain.hid>
To: niklaus.giger@domain.hid
Cc: xenomai@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.