From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 14 Oct 2008 10:01:38 +0000 (GMT) From: Gabriele Moabiti MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-204381555-1223978498=:75012" Message-ID: <621300.75012.qm@domain.hid> Subject: Re: [Xenomai-help] trap exceptions in user List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Xenomai help --0-204381555-1223978498=:75012 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >>> You should trace the exception path in the I-pipe patch to find the=0A>= >> point where your exception handling callback is not called.=0A>> =0A>> = will it be a large print work or there are another ways to do that?=0A>> :)= =0A>=0A> Yes, a small printk works. There is not that much code involved.= =0A=0AI have found the problem.=0AI used a printf some instructions before = the call to the asm blob.=0AOnce removed seems to work as expected.=0AI've = seen also that writing=0A printf(expr); \=0A rt_task_set_mode(0, = T_PRIMARY, 0);=0Ait works (I think printf does a switch to secondary domain= ).=0ANow I should use a user-space-no-problem print like rtdm_printk in ker= nel space.=0AThe docs says rtdm_in_rt_context and rtdm_printk are avalaible= but in the rtdm.h=0Athere is no trace of them and I can't use rtdm_driver.= h 'cause it's kernel only...=0A=0A Gabriele=0A=0A=0A Scopri il blog= di Yahoo! Mail:=0ATrucchi, novit=C3=A0 e scrivi la tua opinione.=0Ahttp://= www.ymailblogit.com/blog --0-204381555-1223978498=:75012 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

&= gt;>> You should trace the exception path in the I-pipe patch to find= the
>>> point where your exception handling callback is = not called.
>>
>> will it be a large print work or there= are another ways to do that?
>> :)
>
> Yes, a small p= rintk works. There is not that much code involved.

I have found the = problem.
I used a printf some instructions before the call to the asm bl= ob.
Once removed seems to work as expected.
I've seen also that writi= ng
      printf(expr); \
   &= nbsp; rt_task_set_mode(0, T_PRIMARY, 0);
it works (I think printf does a switch to secondary domain).
Now I should use a user-space-no-pr= oblem print like rtdm_printk in kernel space.
The docs says rtdm_in_rt_c= ontext and rtdm_printk are avalaible but in the rtdm.h
there is no trace= of them and I can't use rtdm_driver.h 'cause it's kernel only...

&n= bsp;   Gabriele

=0A=0A=0A=0A Scopri il Blog di Yahoo! Mail: trucchi, novit=C3=A0,= consigli... e scrivi la tua opinione! --0-204381555-1223978498=:75012--