From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10516 invoked by alias); 17 Jan 2012 13:40:00 -0000 Received: (qmail 10508 invoked by uid 22791); 17 Jan 2012 13:39:59 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 17 Jan 2012 13:39:47 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0C9692BB252; Tue, 17 Jan 2012 08:39:46 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4Z6oy5OFkLAU; Tue, 17 Jan 2012 08:39:45 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 824E92BB24D; Tue, 17 Jan 2012 08:39:45 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id E7043145616; Tue, 17 Jan 2012 17:39:13 +0400 (RET) Date: Tue, 17 Jan 2012 13:42:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Jan Kratochvil , gdb-patches@sourceware.org Subject: Re: [patch] New set auto-load-local-gdbinit + disable it by default Message-ID: <20120117133913.GX31383@adacore.com> References: <20120117095552.GA6141@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00591.txt.bz2 > I think this is a draconian measure. It prevents me from having a > .gdbinit file loaded automatically as appropriate for a program I'm > debugging. Prominent examples include GDB itself and Emacs, which > both come with a .gdbinit file that makes debugging much easier. I tend to agree as well, although I would not object as strongly. If we do move forward on that change, I think we should do it more gradually: 1. We start by emitting a warning when seeing a local .gdbinit file, but otherwise read it. 2. We stop reading them once a release with the warning is out. > > And "gdb -x ./.gdbinit" is a pretty simple way to do what one wants to do. > > "gdb -x .gdbinit" is much longer than just "gdb". It could really > make a difference in some special use cases, e.g. when you need to > attach to a failing process very quickly. It is also easy to forget. I also agree it's (too) easy to forget. -- Joel