From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 93424 invoked by alias); 13 May 2015 08:06:00 -0000 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 Received: (qmail 93414 invoked by uid 89); 13 May 2015 08:05:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 13 May 2015 08:05:58 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t4D85rGb019913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 13 May 2015 04:05:54 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t4D85ppF018795; Wed, 13 May 2015 04:05:52 -0400 Message-ID: <555305DF.5050704@redhat.com> Date: Wed, 13 May 2015 08:06:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Doug Evans CC: Gary Benson , gdb-patches , Philippe Waroquiers Subject: Re: [PATCH] Make only user-specified executable filenames sticky References: <20150505151448.GA1417@blade.nx> <1430907977-30605-1-git-send-email-gbenson@redhat.com> <5551D7AD.8080500@redhat.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-05/txt/msg00297.txt.bz2 On 05/12/2015 04:49 PM, Doug Evans wrote: > On Tue, May 12, 2015 at 3:36 AM, Pedro Alves wrote: >> On 05/11/2015 09:23 PM, Doug Evans wrote: >>> On Wed, May 6, 2015 at 3:26 AM, Gary Benson wrote: >> >>>> This commit updates GDB to keep track of which executable filenames >>>> were supplied by the user. When GDB might attempt to determine an >>>> executable filename and one is already set, filenames determined by >>>> GDB may be overridden but user-supplied filenames will not. >>> >>> I can imagine sometimes wanting either behaviour, depending on >>> the situation. >> >> Yeah, AFAICS, both examples you gave work the same before >> and after Gary's patch. >> >>> E.g., if I supply a file name do some stuff, and then change >>> my mind or wish to investigate a difference process I may >>> wish gdb to automagically pick up the file name of the new process. >> >> In that case, one can use "file; attach PID". >> >> That is, you can just unload the previous program, so that GDB picks >> up the new one automatically on next attach. > > I realize one *could* do that. > Thing is, someone's muscle memory may make them expect > "attach PID" to Just Work. > After all, "bash$ gdb" + "(gdb) attach PID" Just Works. > > Plus that's two steps. > Why do I *have* to first type "file" with no arguments? > (Joe User may be thinking) > The difference in the two scenarios is explainable, but there's > still an incongruity here. > > We go to lengths to reduce typing in the CLI session. > IWBN if one could type, say, > "attach -f PID" (f for "force gdb to use the binary of the attached process", > or whatever). We're kind of going on a tangent now. While I agree that streamlining the sequence of commands is desirable, I don't think it fixes the issue with muscle memory you raise. For the very same reason, you'll forget to use "attach -f PID" instead of "attach PID". A warning (or query but that may be annoying) may be the best bet for that. Thanks, Pedro Alves