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

[Philippe Gerum <rpm@xenomai.org>]

On 08/06/2015 05:23 PM, Philippe Gerum wrote:
> On 08/06/2015 05:00 PM, Charles Kiorpes wrote:
>>> Could you --enable-debug, and have gdb determine the offending
>>> instruction? TIA,
>>
>> The gdb output is as follows:
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> get_free_range (heap=heap@entry=0x6dc07000, bsize=bsize@entry=256, log2size=8)
>>     at ../../../xenomai-3.0-rc6/lib/copperplate/heapobj-pshared.c:242
>> 242                                           freepage =
>> __shref_check(heap, *((memoff_t *)freepage));
>>
>> Thanks,
>> - Charles
>>
> 
> This may be a memory corruption issue, some metadata from the shared
> heap got trashed earlier in the init sequence.
> 
> Would it be practical to switch this app to the mercury core (no need
> for preempt-rt, just a plain regular desktop kernel), only for the
> purpose of running the init phase over valgrind? That would entail
> stubbing/bypassing the hardware-related inits (e.g. drivers) if ever
> possible.
> 

Also, does this bug happen with --disable-pshared?

-- 
Philippe.