Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Steven Trollope <trollope@lucent.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Linux Realtime Scheduling Option
Date: Mon, 21 Mar 2005 19:21:00 -0000	[thread overview]
Message-ID: <423F1E62.6020008@lucent.com> (raw)
In-Reply-To: <20050318181204.GA31713@nevyn.them.org>

Hi Daniel,

Our application does change its own priority, but I was concerned with 
the priority of gdbserver/gdb. Which Linux tools are you referring to? 
I'll go take a look at them.

In our environment gdb/gdbserver should always run realtime at a set 
priority. Help me understand why is it not a good idea to have 
gdb/gdbserver set its own priority based on an option in .gdbinit?

Thanks much!
Dave

Daniel Jacobowitz wrote:

>On Fri, Mar 18, 2005 at 10:29:32AM -0600, David Steven Trollope wrote:
>  
>
>>Hello!
>>
>>I'm working on a project that uses Linux 2.4 on a PowerPC processor with 
>>real time scheduling.
>>
>>One of the issues we've encountered is that when the application being 
>>debugged is running real time and gdb/gdbserver is not, scheduling 
>>problems occur.
>>
>>I'm wondering if its possible to have an option added to gdb and the 
>>.gdbinit file which specifies the realtime priority which gdb/gdbserver 
>>should run at.
>>
>>I searched the mailing list and do not find anything related to this in 
>>the past.
>>
>>Has anyone got experience in this area? Do patches already exist?
>>    
>>
>
>This is not a good idea.  There are existing Linux tools to change the
>realtime priority of a process; why can't you use them to change the
>priority of the debugger?  You can even do this after starting the
>inferior process if it isn't smart enough to reset its own priority.
>
>  
>

-- 
                 Dave Trollope
            Tel/Fax: +1 630 713 9110
           mailto:trollope@lucent.com
     http://nwswww.ih.lucent.com/~dtrollop/
  http://www.geocities.com/SiliconValley/7499/




  reply	other threads:[~2005-03-21 19:21 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 [this message]
2005-03-21 19:33                           ` Daniel Jacobowitz
2005-03-22  3:04                             ` Dave Trollope
2005-03-22  4:06                               ` Daniel Jacobowitz

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=423F1E62.6020008@lucent.com \
    --to=trollope@lucent.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.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