[Xenomai-help] valgrind

[Xenomai-help] valgrind

[Stéphane ANCELOT]

Hi,
I tried xenomai integration in valgrind .

I have got some problems with __native_muxid  .

Is there an easy way to retrieve this value (is it a const?) or is it a 
variable I have to store and reuse ?


Best Regards
S.Ancelot

Re: [Xenomai-help] valgrind

[Gilles Chanteperdrix]

On Wed, May 28, 2008 at 9:33 AM, Stéphane ANCELOT <sancelot@domain.hid> wrote:
> Hi,
> I tried xenomai integration in valgrind .
>
> I have got some problems with __native_muxid  .
>
> Is there an easy way to retrieve this value (is it a const?) or is it a
> variable I have to store and reuse ?

The muxid is returned by the "xn_sys_bind" system skin syscall. So,
you have to get it at run-time.

-- 
 Gilles

Re: [Xenomai-help] valgrind

[Stéphane ANCELOT]

Gilles Chanteperdrix a écrit :
> On Wed, May 28, 2008 at 9:33 AM, Stéphane ANCELOT <sancelot@domain.hid> wrote:
>   
>> Hi,
>> I tried xenomai integration in valgrind .
>>
>> I have got some problems with __native_muxid  .
>>
>> Is there an easy way to retrieve this value (is it a const?) or is it a
>> variable I have to store and reuse ?
>>     
>
> The muxid is returned by the "xn_sys_bind" system skin syscall. So,
> you have to get it at run-time.
>
>   
OK, but unfortunately, in valgrind, there is a static syscall_table 
containing all  syscalls numbers.

In order solving this problem, I may setup  a static range of syscalls 
for xenomai  and route to concerned valgrind syscall  at execution ?
What are the xenomai syscall ranges ?

Best Regards
S.Ancelot

Re: [Xenomai-help] valgrind

[Gilles Chanteperdrix]

On Thu, May 29, 2008 at 10:53 AM, Stéphane ANCELOT <sancelot@domain.hid> wrote:
>
>
> Gilles Chanteperdrix a écrit :
>>
>> On Wed, May 28, 2008 at 9:33 AM, Stéphane ANCELOT <sancelot@domain.hid>
>> wrote:
>>
>>>
>>> Hi,
>>> I tried xenomai integration in valgrind .
>>>
>>> I have got some problems with __native_muxid  .
>>>
>>> Is there an easy way to retrieve this value (is it a const?) or is it a
>>> variable I have to store and reuse ?
>>>
>>
>> The muxid is returned by the "xn_sys_bind" system skin syscall. So,
>> you have to get it at run-time.
>>
>>
>
> OK, but unfortunately, in valgrind, there is a static syscall_table
> containing all  syscalls numbers.

You have to modify valgrind to allow Xenomai dynamic syscall table scheme.

>
> In order solving this problem, I may setup  a static range of syscalls for
> xenomai  and route to concerned valgrind syscall  at execution ?
> What are the xenomai syscall ranges ?

It depends on the platform, but what we know for sure is that Xenomai
syscall ranges are out of Linux syscall ranges. You will find Xenomai
syscall number mangling scheme in include/asm-yourplatform/syscall.h,
and the syscall numbers of a given skin in include/yourskin/syscall.h.

-- 
 Gilles