From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] [PATCH] Unfreeze timers when debugged target exits
Date: Fri, 09 May 2008 11:44:17 +0200 [thread overview]
Message-ID: <48241CF1.8020708@domain.hid> (raw)
In-Reply-To: <4824197E.90709@domain.hid>
Jan Kiszka wrote:
> I expressed my skepticism about this global timer freeze before :->, and
Just try debugging periodic code without it...
We should have an opt-out mechanism to hide timers from the auto-freeze feature,
that is the real issue yet to be fixed.
> now it hit me unpleasantly (Customer: "Is it normal that Xenomai stops
> working after the gdb session?" Jan [scratching head]: "Hmm, no...").
>
> After more scratching I think I found the reason: The target decided to
> die after some fault, but Xenomai missed to unfreeze the timers. Patch
> below fixes that.
>
> Without hearing complains, this also goes into trunk/2.4.x later today.
>
> Jan
>
> ---
> ksrc/nucleus/shadow.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> Index: b/ksrc/nucleus/shadow.c
> ===================================================================
> --- a/ksrc/nucleus/shadow.c
> +++ b/ksrc/nucleus/shadow.c
> @@ -2148,6 +2148,9 @@ static inline void do_taskexit_event(str
> if (!thread)
> return;
>
> + if (xnthread_test_info(thread, XNDEBUG))
> + unlock_timers();
> +
> if (xnpod_shadow_p())
> xnshadow_relax(0);
>
>
This should be ok.
--
Philippe.
next prev parent reply other threads:[~2008-05-09 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 9:29 [Xenomai-core] [PATCH] Unfreeze timers when debugged target exits Jan Kiszka
2008-05-09 9:35 ` Gilles Chanteperdrix
2008-05-09 9:40 ` Jan Kiszka
2008-05-09 9:44 ` Jan Kiszka
2008-05-09 9:47 ` Philippe Gerum
2008-05-09 9:44 ` Philippe Gerum [this message]
2008-05-09 9:53 ` Gilles Chanteperdrix
2008-05-09 10:06 ` Philippe Gerum
2008-05-09 12:27 ` 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=48241CF1.8020708@domain.hid \
--to=rpm@xenomai.org \
--cc=Xenomai-core@domain.hid \
--cc=jan.kiszka@domain.hid \
/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.