From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55484 invoked by alias); 12 May 2015 10:36:36 -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 55408 invoked by uid 89); 12 May 2015 10:36:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham 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; Tue, 12 May 2015 10:36:34 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id BAE87BDD62; Tue, 12 May 2015 10:36:32 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t4CAaTZY017662; Tue, 12 May 2015 06:36:30 -0400 Message-ID: <5551D7AD.8080500@redhat.com> Date: Tue, 12 May 2015 10:36: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 , Gary Benson CC: 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> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-05/txt/msg00265.txt.bz2 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. Another way to handle that would be to leave the file loaded in inferior 1, and switch to a new inferior to investigate the other process. > OTOH other times I may wish to override what gdb would > automagically choose and supply my own file name. That'd be "file PROGRAM; attach PID". The difference is that with Gary's patch, "attach PID1; attach PID2" just works, while today we don't even get a warning. If for some odd reason, after Gary's patch, the user wants to force the executable of PID1 on PID2, he can still do e.g., "info inferiors; file paste_program_name" before the second attach. We don't have a command to get out of: "file wrong_program; attach PID" that is, a command to issue after the attach to re-fetch the program name from the running process, without detaching first. Though if we had a warning that printed the expected program name, the user could copy/paste from that. Thanks, Pedro Alves