From: Philippe Gerum <rpm@xenomai.org>
To: thomas.debes@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [Xenomai-help] Periodic threads not scheduled anymore during debug session
Date: Sat, 30 May 2009 17:32:33 +0200 [thread overview]
Message-ID: <1243697553.27443.44.camel@domain.hid> (raw)
In-Reply-To: <4B2EEE69E41E524EB7FCDC62A15D68D80348DF91@domain.hid>
On Wed, 2009-05-27 at 11:23 +0200, thomas.debes@domain.hid wrote:
> >
> > For the rest, we would have to reverse the current logic and tag
> > blockable timers instead of non-blockable one. The shadow code would
> > then have to tag the ptimer/rtimer of the ptraced thread as blockable,
> > leaving all other timers as unblockable by default.
> >
> > >
>
> Do you know when this will be implemented?
>
No idea, yet. This is certainly something to work on at some point
though.
> We have a kernel watchdog service running (Xenomai task) which always restarts our system while debugging (because the watchdog is not triggered anymore). I assume that this problem is related to the one above.
>
> Thanks
> Thomas
>
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
--
Philippe.
prev parent reply other threads:[~2009-05-30 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 12:04 [Xenomai-help] Periodic threads not scheduled anymore during debug session Steven Kauffmann
2009-05-13 12:59 ` [Xenomai-core] " Philippe Gerum
2009-05-13 13:16 ` Gilles Chanteperdrix
2009-05-13 13:30 ` Philippe Gerum
2009-05-13 13:34 ` Gilles Chanteperdrix
2009-05-13 13:42 ` Philippe Gerum
2009-05-27 9:23 ` thomas.debes
2009-05-30 15:32 ` Philippe Gerum [this message]
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=1243697553.27443.44.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=thomas.debes@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.