From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 58366 invoked by alias); 5 Jun 2018 21:16:13 -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 16419 invoked by uid 89); 5 Jun 2018 21:15:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=Personally X-HELO: mailsec118.isp.belgacom.be Received: from mailsec118.isp.belgacom.be (HELO mailsec118.isp.belgacom.be) (195.238.20.114) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Jun 2018 21:15:20 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2AdBAAu/BZb/2wz8VFcHAEBAQQBAQoBA?= =?us-ascii?q?YNDZ2gShCCIY44JMQGWEwsrAYQ6BAICgh8iOBQBAgEBAQEBAQIBayiCNSQBgk8?= =?us-ascii?q?BBSMzIxAIAxgCAiYCAjkeBgGFOadHghyEWYNpgWiBC4kLP4NtLodzglQCmHQHA?= =?us-ascii?q?oFnjQGNIJEmgVghgVJtgxeCR44IPYE9CAwBjicBAQ?= X-IPAS-Result: =?us-ascii?q?A2AdBAAu/BZb/2wz8VFcHAEBAQQBAQoBAYNDZ2gShCCIY44?= =?us-ascii?q?JMQGWEwsrAYQ6BAICgh8iOBQBAgEBAQEBAQIBayiCNSQBgk8BBSMzIxAIAxgCA?= =?us-ascii?q?iYCAjkeBgGFOadHghyEWYNpgWiBC4kLP4NtLodzglQCmHQHAoFnjQGNIJEmgVg?= =?us-ascii?q?hgVJtgxeCR44IPYE9CAwBjicBAQ?= Received: from 108.51-241-81.adsl-dyn.isp.belgacom.be (HELO md) ([81.241.51.108]) by relay.skynet.be with ESMTP/TLS/AES256-GCM-SHA384; 05 Jun 2018 23:15:16 +0200 Message-ID: <1528233316.1703.31.camel@skynet.be> Subject: Re: [PATCHv2 2/2] gdb: Change how frames are selected for 'frame' and 'info frame'. From: Philippe Waroquiers To: Andrew Burgess , Eli Zaretskii Cc: gdb-patches@sourceware.org Date: Tue, 05 Jun 2018 21:16:00 -0000 In-Reply-To: <20180605185318.GE15881@embecosm.com> References: <63020671a997f926cd747677cd4e614e51e81f8d.1525797846.git.andrew.burgess@embecosm.com> <83k1sanw3t.fsf@gnu.org> <20180521115357.GS3797@embecosm.com> <83y3gddl5q.fsf@gnu.org> <20180605185318.GE15881@embecosm.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00129.txt.bz2 On Tue, 2018-06-05 at 19:53 +0100, Andrew Burgess wrote: > > If we do need a keyword, how about "frame add"? > > Personally, I think 'add' is worse than 'create' - what's the frame > being added too? But I do acknowledge that 'create' is not ideal > either. > > I wonder if 'new' is better than 'create', maybe implies less "making > something in the inferior"? Or how about, 'for' instead, like this: > > (gdb) frame for STACK-ADDR PC-ADDR If nothing is added or created or ..., maybe you could also use one of: (gdb) frame interpret STACK-ADDR PC-ADDR or (gdb) frame look STACK-ADDR PC-ADDR or (gdb) frame view STACK-ADDR PC-ADDR ? Philippe