[Xenomai] Some Information About compilation Xenomai and RT Patches

Stoidner, Christoph c.stoidner at arvero.de
Mon Jun 23 12:04:37 CEST 2014

Original ipipe-3.10.18 without Preempt-RT works without any problem. The problem occurs only in combination of my Preempt-RT merge and enabled FCSE in guaranteed mode.

Since unmodified ipipe-3.10 does not show the problem I assume unmodified ipipe-3.14 also does not show the problem. Or do you think 3.14 brings some more details?


Von: Gilles Chanteperdrix <gilles.chanteperdrix at xenomai.org>
Gesendet: Montag, 23. Juni 2014 11:53
An: Stoidner, Christoph; xenomai at xenomai.org
Betreff: Re: [Xenomai] Some Information About compilation Xenomai and RT Patches

On 06/23/2014 11:33 AM, Stoidner, Christoph wrote:
> Hi Gilles,
> when a userspace application starts it calls the brk() syscall to
> enlarge it's heap space. In some cases the call leads to an NOMEM
> error in fcse_check_mmap_addr(). Since glibc does not handle NOMEM
> error at this place the a segfault exception appears.
> It seems as this happens when brk() got an address above some limit,
> also when the process at all consumes less than 32MB RAM. E.g.
> busybox shell command "ls" is enough to get the segfault.

Could you test the I-pipe git branch ipipe-3.14, unmodified?


More information about the Xenomai mailing list