From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9041 invoked by alias); 17 Jan 2012 21:10:17 -0000 Received: (qmail 9033 invoked by uid 22791); 17 Jan 2012 21:10:16 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 17 Jan 2012 21:10:01 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LXY00100O2RWI00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Tue, 17 Jan 2012 23:09:59 +0200 (IST) Received: from HOME-C4E4A596F7 ([84.229.115.9]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LXY001U3O4MNR90@a-mtaout20.012.net.il>; Tue, 17 Jan 2012 23:09:59 +0200 (IST) Date: Tue, 17 Jan 2012 21:13:00 -0000 From: Eli Zaretskii Subject: Re: [patch] New set auto-load-local-gdbinit + disable it by default In-reply-to: To: Tom Tromey Cc: jan.kratochvil@redhat.com, dje@google.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ty3u3uj1.fsf@gnu.org> References: <20120117095552.GA6141@host2.jankratochvil.net> <20120117162621.GA3883@host2.jankratochvil.net> <837h0q5i4u.fsf@gnu.org> <20120117175957.GA9415@host2.jankratochvil.net> X-IsSubscribed: yes 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/msg00651.txt.bz2 > From: Tom Tromey > Cc: Eli Zaretskii , dje@google.com, gdb-patches@sourceware.org > Date: Tue, 17 Jan 2012 13:28:29 -0700 > > >>>>> "Jan" == Jan Kratochvil writes: > > Jan> On Tue, 17 Jan 2012 18:54:57 +0100, Eli Zaretskii wrote: > >> ??? How's the .gdbinit file that comes with Emacs "malicious"? > > Jan> If one runs "gdb" one expects to get "gdb". > > Jan> If one runs "gdb" in any of these directories (Emacs) one surprisingly gets > Jan> some weirdly behaving beast instead. > > I'm not convinced by this line of argument. > > I think gdb has touted this -- rightly -- as a feature. And, if > anything, I think we've gone even more in this direction in recent > years, what with pretty-printers and Python auto-loading. Furthermore, > I think this is a good trend in general; applications are getting more > complex, and this provides an important way to adapt the debugger to > them. > > That said, I agree with your conclusions for other reasons. If those other reasons are safety, then this is not the way to do it. Legitimate uses of .gdbinit of many should not be precluded on behalf of potential wrong-doing of the few. If safety is our concern, we should make unsafe uses harder or impossible without hurting safe uses.