Re: [Xenomai-help] shared memory mlockall error w/ mono interpreter?

[Henry Bausley <hbausley@domain.hid>]

This problem seemed to be caused by the boehm garbage collector used in
mono.  The Boehm garbage collector uses SIGXCPU and SIGPWR to
synchronize cross-thread garbage collection.  Recompiling the mono
garbage collector to use a different signal values (SIGRTMIN + 5)
instead of SIGXCPU seems to have solved the problem. Does this make
sense.



On Tue, 2008-12-02 at 10:25 -0800, Henry Bausley wrote:
> The mono application doesn't need realtime services.  But it does need
> access to DPRAM.
> 
> It crashes with the message:
> Xenomai: process memory not locked (missing mlockall?)
> 
> On Fri, 2008-11-21 at 10:55 +0100, Gilles Chanteperdrix wrote:
> > Henry Bausley wrote:
> > > We have an application that uses shared memory to communicate from our
> > > kernel driver to user space.  In our own standard C applications we can
> > > issue an mlockall and we can use multiple threads without a problem.
> > > 
> > > However, we are also using the mono .NET interpreter which links to a
> > > shared library that links to the xenomai shared memory and issues a
> > > mlockall.  Whenever we run programs using the mono interpreter we get
> > > the error message Xenomai: process memory not locked (mlockall).  mono
> > > is a .NET virtual machine w/ garbage collection like java.
> > 
> > Does the mono application need real-time services ?
> > 
> > > 
> > > We tried --enable-posix-auto-mlockall but the third party apps running
> > > under mono still crashes with the mlockall
> > 
> > How does it crash ? Not enough memory ?
> >