From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124760 invoked by alias); 8 Jul 2015 20:16:22 -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 124734 invoked by uid 89); 8 Jul 2015 20:16:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-HELO: mail-wg0-f53.google.com Received: from mail-wg0-f53.google.com (HELO mail-wg0-f53.google.com) (74.125.82.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 08 Jul 2015 20:16:18 +0000 Received: by wgov12 with SMTP id v12so20993056wgo.1 for ; Wed, 08 Jul 2015 13:16:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=9RjS/GmFoR7tCy2ugUeO8aeNHVZkMC1WrRw0MuEB2TM=; b=Z9Z2ff9b/rGZw4evpKhLRTorsWkhFr2T8pK9gl3e8uOF2DH3gbxfUh3uORq9VhIRfw /+zyOPfEwfgMmduAoU6DkB5xQBQgZAsmOkrovbbci0kWIuZBWklh6N2L/KRlkbRyvBtV vqPZqw4YDoE2OFFOh92xQckDXHqYSilqrYyQ4ulvVK5/bEBy5Ns5JoPhBh1XHUeMxc3V TKbcfVc4PpuL1dckvkjx+I2C86zVNNPAVk75t/dXsVYAMsRrv6aGEUVWkZXoCCTqOot/ axJ9TErPFKGc/JkUy5g9iFGQlhxDgqxziSTmL18SZzV0cZEwk/iP0a6asm4F4idNK+o4 rH5w== X-Gm-Message-State: ALoCoQndRkz+ZY/QZq9lRaEx+dckvCLCCIsQWgszLVUhObxPkAmUhgQwWhooL5pCcqnzeqLVS5Ji X-Received: by 10.194.86.161 with SMTP id q1mr23724661wjz.18.1436386575958; Wed, 08 Jul 2015 13:16:15 -0700 (PDT) Received: from localhost (host81-158-4-174.range81-158.btcentralplus.com. [81.158.4.174]) by smtp.gmail.com with ESMTPSA id ei8sm5122276wjd.32.2015.07.08.13.16.14 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Jul 2015 13:16:15 -0700 (PDT) Date: Wed, 08 Jul 2015 20:16:00 -0000 From: Andrew Burgess To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [RFC] Use of create_new_frame from 'frame'. Message-ID: <20150708201613.GD17985@embecosm.com> References: <20150708170944.GA17985@embecosm.com> <83io9uv3lb.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83io9uv3lb.fsf@gnu.org> X-Editor: GNU Emacs [ http://www.gnu.org/software/emacs ] User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes X-SW-Source: 2015-07/txt/msg00255.txt.bz2 * Eli Zaretskii [2015-07-08 22:42:08 +0300]: > > Date: Wed, 8 Jul 2015 18:09:44 +0100 > > From: Andrew Burgess > > > > I wonder then if there's a better way to offer this feature. The two > > possible choices (other suggestions welcome) are: > > > > 1. Create a new command 'create-frame' that takes one or two > > arguments, and always creates and selects a new frame new frame. > > The frame command no longer creates new frames. > > > > 2. Make 'frame' take an (optional) flag (like 'x', or > > 'disassemble'), so a user can now say: > > frame /c STACK-ADDR PC-ADDR > > in order to create (and select) a new frame. Without the /c flag > > no new frames are created. With the flag only new frames are > > created, old frames are not selected. > > You could also ask the user for confirmation, when the command is > going to create a new frame. That's certainly a possible option. I didn't list it as it does not in itself solve the problem of different length backtraces preventing the creation of frames; a backtrace of length 100 means the user can't create a frame at address 100. Thanks, Andrew