Re: [Xenomai] Segfaults and ENOMEM during rt_event_create()

[Philippe Gerum <rpm@xenomai.org>]

On 08/10/2015 05:17 PM, Charles Kiorpes wrote:
>> Is this case (trying to create an event flag with a conflicting name)
>> part of the original scenario with Cobalt?
> 
> This rt_event_create() with existing name occurs a little earlier in
> my application's startup phase than where the segfault occurs using
> Cobalt.  However, applying the rt_event_bind() workaround and
> switching back to Cobalt does not change the segfault behavior (it
> still occurs at the same place), so I'm not convinced that they're
> related.
> 
> When I run the processes through Valgrind using the Mercury core and
> checking event existence with rt_event_bind() before attempting to
> create, Valgrind finds no issues.  The application hangs at a
> different location (creation of a periodic task; I'm fairly certain
> that I just need to rework that section of code a little).
> 
> However, my application really need the tight timings that Cobalt
> provides, and this has to eventually run on an embedded system, so
> switching to Mercury is not a viable solution.
> 

You should retry with the current head of the -next branch with Cobalt.
No guarantee, but several fixes took place in the shared heap
implementation. Since I don't know much about your application, I can
only assume that one of them might help. At the very least, this is a
better starting point than -rc6.

-- 
Philippe.