From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4542 invoked by alias); 17 Jan 2012 16:57:00 -0000 Received: (qmail 4533 invoked by uid 22791); 17 Jan 2012 16:56:59 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 17 Jan 2012 16:56:46 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0HGuj5m002995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 17 Jan 2012 11:56:45 -0500 Received: from host2.jankratochvil.net (ovpn-116-21.ams2.redhat.com [10.36.116.21]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q0HGufpr020171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 17 Jan 2012 11:56:44 -0500 Date: Tue, 17 Jan 2012 17:27:00 -0000 From: Jan Kratochvil To: Doug Evans Cc: gdb-patches@sourceware.org Subject: Re: [patch] New set auto-load-local-gdbinit + disable it by default Message-ID: <20120117165640.GB5344@host2.jankratochvil.net> References: <20120117095552.GA6141@host2.jankratochvil.net> <20120117162621.GA3883@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.21 (2010-09-15) 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/msg00606.txt.bz2 On Tue, 17 Jan 2012 17:44:32 +0100, Doug Evans wrote: > ??? I don't understand. I was exaggerating the "(top-gdb)" & co. to be "destructive" but I feel it so. > I also don't understand the reference to making the debugging session > completely unusable. Personally I always feared what is that "(top-gdb)" there and what new breakpoints it created and why it prints complaints which are not printed normally etc. etc., I just rather quit and and run normal GDB for GDB. If I want some special environment (.gdbinit) for GDB-to-GDB I can study the supplied one and _then_ I can load the supplied one. For a newbie it is a needless burden to complicate the debugging of GDB even more. > The user will be surprised if s/he has been using "Makefile" and not > noticing that someone slipped in "GNUmakefile". S/he might see it and > not even know that it trumps his/her own Makefile. GNUmakefile vs. Makefile... OK. But running "make" in untrusted source directory is never safe as Makefile itself is not trusted. While I occasionally do run "gdb -nx file core" on untrusted crash tarballs - supplied by customers. Now I have to use secured VM for it after Python and libthread_db.so.1 automatic loading crept in. Thanks, Jan