All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai help <xenomai@xenomai.org>, Gabriele Moabiti <gabmoa@domain.hid>
Subject: Re: [Xenomai-help] trap exceptions in user
Date: Tue, 14 Oct 2008 14:13:14 +0200	[thread overview]
Message-ID: <48F48CDA.5050402@domain.hid> (raw)
In-Reply-To: <48F472B2.7050302@domain.hid>

Jan Kiszka wrote:
> Gabriele Moabiti wrote:
>>>>> 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 printk 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 blob.
>> Once removed seems to work as expected.
>> I've seen also that writing
>>       printf(expr); \
>>       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-problem print like rtdm_printk in kernel space.
>> The docs says rtdm_in_rt_context 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...
> 
> rtdm_printk (read 'k' as 'kernel') is for driver development in kernel
> space only.
> 
> What you are looking for is rt_printf from the rtdk lib. See related
> example (examples/native/rtprint.c).

I think it would be nice if we had some doxygen documentation for the
rtdk lib. This way, we could point users to this documentation.

-- 
                                                 Gilles.


  reply	other threads:[~2008-10-14 12:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 10:01 [Xenomai-help] trap exceptions in user Gabriele Moabiti
2008-10-14 10:21 ` Jan Kiszka
2008-10-14 12:13   ` Gilles Chanteperdrix [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-24 19:17 Gabriele Moabiti
2008-10-26 23:49 ` Gilles Chanteperdrix
2008-10-24 15:30 Gabriele Moabiti
2008-10-24 13:53 Gabriele Moabiti
2008-10-24 17:43 ` Gilles Chanteperdrix
2008-10-24 17:44   ` Gilles Chanteperdrix
2008-10-15 15:30 Gabriele Moabiti
2008-10-15 15:39 ` Jan Kiszka
2008-10-13  9:55 Gabriele Moabiti
2008-10-11 19:32 Gabriele Moabiti
2008-10-11 19:34 ` Gilles Chanteperdrix
2008-10-11 21:35 ` Philippe Gerum
2008-10-10 17:57 Gabriele Moabiti
2008-10-10 16:02 Gabriele Moabiti
2008-10-10 16:04 ` Gilles Chanteperdrix
2008-10-11 11:24 ` Gilles Chanteperdrix
2008-10-10 15:24 Gabriele Moabiti
2008-10-10 15:38 ` Gilles Chanteperdrix
2008-10-10 13:50 Gabriele Moabiti
2008-10-10 14:00 ` Gilles Chanteperdrix
2008-10-08 11:32 Gabriele Moabiti
2008-10-08 12:29 ` Gilles Chanteperdrix
2008-10-08 10:34 Gabriele Moabiti
2008-10-08 10:50 ` Gilles Chanteperdrix
     [not found] <296620.67855.qm@domain.hid>
2008-10-08 10:09 ` Gilles Chanteperdrix
2008-10-03 12:30 Gabriele Moabiti
2008-10-03 14:58 ` Gilles Chanteperdrix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48F48CDA.5050402@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=gabmoa@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.