From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19016 invoked by alias); 21 Mar 2005 19:33:01 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18961 invoked from network); 21 Mar 2005 19:32:56 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 21 Mar 2005 19:32:56 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DDSe8-0001NS-1l; Mon, 21 Mar 2005 14:33:04 -0500 Date: Mon, 21 Mar 2005 19:33:00 -0000 From: Daniel Jacobowitz To: David Steven Trollope Cc: gdb@sources.redhat.com Subject: Re: Linux Realtime Scheduling Option Message-ID: <20050321193304.GA5205@nevyn.them.org> Mail-Followup-To: David Steven Trollope , gdb@sources.redhat.com References: <01c4f3aa$Blat.v2.2.2$b4217d20@zahav.net.il> <20050106233136.GA29435@white> <4CE93165-C27F-4CF6-90B8-7632A7BD2672@apple.com> <20050107011211.GB29435@white> <41DDFF0D.5040205@netspace.net.au> <20050111193526.GA5699@white> <41E5E102.2010703@lucent.com> <423B01EC.9060509@lucent.com> <20050318181204.GA31713@nevyn.them.org> <423F1E62.6020008@lucent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <423F1E62.6020008@lucent.com> User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00196.txt.bz2 On Mon, Mar 21, 2005 at 01:20:02PM -0600, David Steven Trollope wrote: > 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. Search for 'rt' or 'chrt'; I do not recall which one is current. I believe they are in the 'schedutils' distribution. > 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? First of all, gdbserver doesn't parse an init file. You would have to add a Linux-specific packet type to the remote protocol for GDB to communicate this to gdbserver. Secondly, because there are standalone tools to handle the problem. gdbserver is supposed to be simple; I don't want to add code specific to a particular, fairly uncommon debugging environment when existing tools handle it perfectly well. If you can come up with a reason why the standalone tools can not be used to solve the problem, then we can rediscuss :-) -- Daniel Jacobowitz CodeSourcery, LLC