From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8211 invoked by alias); 31 May 2005 13:27:53 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 8155 invoked by uid 22791); 31 May 2005 13:27:49 -0000 Received: from lakermmtao10.cox.net (HELO lakermmtao10.cox.net) (68.230.240.29) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 31 May 2005 13:27:48 +0000 Received: from white ([68.9.64.121]) by lakermmtao10.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050531132743.ELLR7787.lakermmtao10.cox.net@white> for ; Tue, 31 May 2005 09:27:43 -0400 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1Dd6mU-0003m1-00 for ; Tue, 31 May 2005 09:27:42 -0400 Date: Tue, 31 May 2005 14:42:00 -0000 From: Bob Rossi To: gdb-patches@sourceware.org Subject: Re: RFC: Check permissions of .gdbinit files Message-ID: <20050531132742.GA12857@white> References: <20050530185201.GA29332@nevyn.them.org> <20050530223305.GA2727@nevyn.them.org> <20050530230026.GA3618@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050530230026.GA3618@nevyn.them.org> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-05/txt/msg00661.txt.bz2 On Mon, May 30, 2005 at 07:00:26PM -0400, Daniel Jacobowitz wrote: > On Tue, May 31, 2005 at 12:49:05AM +0200, Andreas Schwab wrote: > > If you have a group of developers working on the same project you might > > want a shared .gdbinit somewhere. > > I'm leaning towards handling that by suggesting in the manual that you > use "source .gdbinit" in $HOME/.gdbinit for that. I agree that it's a > little less convenient. I dunno. The really bad thing about this is that you can't source a generic path. For instance, source $GROUP_GDB_INIT_DIR/.gdbinit Make's it very hard to make the .gdbinit scripts configurable. For instance, since this is for .gdbinit files that are typically not in $HOME, you would probably have one for every program that is built (or something like that). So if you were unfortunate enough to be effected by this change, you would have to change your $HOME/.gdbinit path each time to point to the .gdbinit you wanted to source. This would be annoying. What if we had GDB prompt the user to determine if they wanted to read the .gdbinit file in? Then we could add another configuration variable to GDB that allowed it to always read in the files. That way, by default GDB would be more safe, but for the rest of us, it would work the way it always has. Thanks, Bob Rossi