From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18779 invoked by alias); 17 Jan 2012 19:30:45 -0000 Received: (qmail 18767 invoked by uid 22791); 17 Jan 2012 19:30:44 -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 19:30:31 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0HJUTNn030568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 17 Jan 2012 14:30:30 -0500 Received: from host2.jankratochvil.net (ovpn-116-21.ams2.redhat.com [10.36.116.21]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q0HJUQiv014163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 17 Jan 2012 14:30:28 -0500 Date: Tue, 17 Jan 2012 19:37:00 -0000 From: Jan Kratochvil To: Matt Rice Cc: Doug Evans , gdb-patches@sourceware.org Subject: Re: [patch] New set auto-load-local-gdbinit + disable it by default Message-ID: <20120117193025.GA16444@host2.jankratochvil.net> References: <20120117095552.GA6141@host2.jankratochvil.net> <20120117162621.GA3883@host2.jankratochvil.net> <20120117165640.GB5344@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/msg00621.txt.bz2 On Tue, 17 Jan 2012 20:20:09 +0100, Matt Rice wrote: > On Tue, Jan 17, 2012 at 9:26 AM, Doug Evans wrote: > > I, OTOH, like the (top-gdb) prompt. > > FWIW I found it insufficient, and avoid the gdb/.gdbinit so rewrote it > in python so i get BTW not so recently but in some years ago GDB usually crashed (=problem B) while I was debugging GDB for problem A. So I had commonly running then three GDBs in row (to have the problem B reproducible), so "top-gdb" would not be sufficient (if I used it) anyway. Regards, Jan