From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15723 invoked by alias); 26 Jun 2004 09:10:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15707 invoked from network); 26 Jun 2004 09:10:10 -0000 Received: from unknown (HELO nick.uklinux.net) (194.247.50.105) by sourceware.org with SMTP; 26 Jun 2004 09:10:10 -0000 Received: by nick.uklinux.net (Postfix, from userid 501) id 5A9F075FDE; Sat, 26 Jun 2004 10:08:42 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16605.15641.474398.42157@nick.uklinux.net> Date: Sat, 26 Jun 2004 09:10:00 -0000 To: Daniel Jacobowitz , Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: How does GDB/MI give the current frame In-Reply-To: <20040624231659.GA16577@nevyn.them.org> References: <16603.23348.569889.284030@nick.uklinux.net> <20040624231659.GA16577@nevyn.them.org> X-SW-Source: 2004-06/txt/msg00257.txt.bz2 Daniel Jacobowitz writes: DJ> DJ> Why not use -stack-info-frame? Because AFAIK this MI command has not been implemented (yet). Andrew Cagney writes: AC> When the user does "up", "down", the debugger should generate a selected AC> CLI frame changed event (it currently doesn't). If the GUI so chooses, AC> it can track the users "selected" frame, by responding to these events. I don't know what a selected CLI frame changed event is but up, down, and frame generate MI output, so I imagine its just a case of hooking -stack-info-frame and -stack-select-frame to that output. I will try to do this if you think it's appropriate. Nick