From: Daniel Jacobowitz <drow@false.org>
To: Dave Trollope <trollope@lucent.com>
Cc: gdb@sources.redhat.com
Subject: Re: Linux Realtime Scheduling Option
Date: Tue, 22 Mar 2005 04:06:00 -0000 [thread overview]
Message-ID: <20050322040557.GA25752@nevyn.them.org> (raw)
In-Reply-To: <423F8B07.9010603@lucent.com>
On Mon, Mar 21, 2005 at 09:03:35PM -0600, Dave Trollope wrote:
> Perhaps gdb/gdbserver could have a command line option (instead of
> .gdbinit) that registers itself realtime, as the highest priority? Its
> likely you want the debugger to run at the highest priority to catch
> tight loops etc. This would also map to non-unix OSs like VxWorks.
>
> Does this strategy sound more appealing?
No, because this is exactly what you would accomplish by using rt/chrt.
Please, look at them before we continue this conversation.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-03-22 4:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1093622671.2836.ezmlm@sources.redhat.com>
2004-08-27 17:56 ` GDB/MI Output Syntax Jim Ingham
2004-08-27 19:12 ` Michael Chastain
2005-01-05 23:27 ` Bob Rossi
2005-01-06 4:48 ` Eli Zaretskii
2005-01-06 23:31 ` Bob Rossi
2005-01-07 0:36 ` Jim Ingham
2005-01-07 1:12 ` Bob Rossi
2005-01-07 3:12 ` Russell Shaw
2005-01-11 19:35 ` Bob Rossi
2005-01-13 2:23 ` Bob Rossi
2005-01-13 2:46 ` Intrusive GDB Symbol Lookup when debugging remotely David Steven Trollope
2005-01-22 4:25 ` Dave Trollope
2005-01-24 19:48 ` Andrew Cagney
2005-01-24 19:54 ` David Steven Trollope
2005-03-18 16:29 ` Linux Realtime Scheduling Option David Steven Trollope
2005-03-18 18:12 ` Daniel Jacobowitz
2005-03-21 19:21 ` David Steven Trollope
2005-03-21 19:33 ` Daniel Jacobowitz
2005-03-22 3:04 ` Dave Trollope
2005-03-22 4:06 ` Daniel Jacobowitz [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=20050322040557.GA25752@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=trollope@lucent.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).