Re: [Xenomai] gdb / threads on beaglebone black

[Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>]

On 05/28/2014 04:45 PM, Michael Haberler wrote:
> 
> Am 28.05.2014 um 16:24 schrieb Philippe Gerum <rpm@xenomai.org>:
> 
>> On 05/28/2014 04:08 PM, Drew wrote:
>>> Yes, my guess was correct.
>>> The do - while loop in trampoline is exiting with error -38 (-ENOSYS?)
>>> If I change line 110 of skins/native/task.c:
>>>
>>> - while(err == -EINTR)
>>> + while(err == -EINTR || err == -ENOSYS)
>>>
>>> then I'm able to single-step in gdb. :-)
>>>
>>> Is my change a hack, or is it the correct thing to do?
> 
> I reproduced the behavior on an slightlier earlier kernel version than Drew used:
> 
> config: http://static.mah.priv.at/public/config.txt
> dmesg: http://static.mah.priv.at/public/dmesg.txt
> 
> $ cat /proc/ipipe/version
> 3
> $ cat /proc/xenomai/version
> 2.6.3
> 
>>
>> No Xenomai call should ever return ENOSYS. Something is definitely wrong with the current setup.
>>
>>> It looks like rt_task_trampoline is only expecting EINTR to occur. Is
>>> some other bug causing ENOSYS?
>>
>> This means that the 'barrier' syscall did not get to Xenomai core, but was rejected as undefined.
>>
>> Could any of the hints mentioned here apply in your case?
>> http://www.xenomai.org/documentation/xenomai-2.6/html/TROUBLESHOOTING/#_any_xenomai_service_fails_with_code_38_enosys
> 
> as above, I'm not seeing a violation of any of those conditions?

Is there no message printed on the kernel console which would explain
why this syscall gets rejected?


-- 
                                                                Gilles.