All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] RTDM task blocks when connecting gdb to realtime task
Date: Fri, 20 Aug 2010 16:08:57 +0200	[thread overview]
Message-ID: <4C6E8C79.1050501@domain.hid> (raw)
In-Reply-To: <1282313187.1730.611.camel@domain.hid>

Philippe Gerum wrote:
> On Fri, 2010-08-20 at 15:58 +0200, Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>>>  However, terminating gdb and restarting app outside gdb
>>>> does make RTDM task resume execution. Before, the driver had to be reloaded.
>>>>
>>>> So gdb appears to be causing timer to block even if no breakpoint is set,
>>>> probably signals?
>>>>
>>> There is no reason for that. Sending "continue" to gdb is expected to
>>> unblock the timers, until the code is single-stepped again (e.g. after
>>> ^C or any breakpoint).
>> gdb silently intercepts a traced program for various reasons, e.g.
>> thread creation or library loading. Even if no user breakpoint is set,
>> the program may briefly be stopped nevertheless. If that happens
>> frequently enough, and every stop can add latencies to running timers...
> 
> We are talking about permanent freeze of timers, not transient (at least
> this is what I got from the ongoing discussion).

Yes, but what would happen if the interruption rate is higher than the
timer delay? Wouldn't we effectively end up with a permanent freeze?

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2010-08-20 14:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 16:03 [Xenomai-help] RTDM task blocks when connecting gdb to realtime task Herrera-Bendezu, Luis
2010-08-18 16:20 ` Gilles Chanteperdrix
2010-08-18 16:38 ` Philippe Gerum
2010-08-18 17:29   ` Herrera-Bendezu, Luis
2010-08-18 20:44     ` Philippe Gerum
2010-08-19 12:26       ` Herrera-Bendezu, Luis
2010-08-19 16:42         ` Philippe Gerum
2010-08-19 17:13           ` Herrera-Bendezu, Luis
2010-08-20  5:39             ` Philippe Gerum
2010-08-20  6:03               ` Philippe Gerum
2010-08-20 13:30               ` Herrera-Bendezu, Luis
2010-08-20 13:49                 ` Philippe Gerum
2010-08-20 13:58                   ` Jan Kiszka
2010-08-20 14:06                     ` Philippe Gerum
2010-08-20 14:08                       ` Jan Kiszka [this message]
2010-08-20 14:24                         ` Philippe Gerum
2010-08-20 14:25                         ` Herrera-Bendezu, Luis
2010-08-20 14:41                           ` Philippe Gerum

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=4C6E8C79.1050501@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rpm@xenomai.org \
    --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.