From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16567 invoked by alias); 11 Jul 2004 22:49:23 -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 16547 invoked from network); 11 Jul 2004 22:49:22 -0000 Received: from unknown (HELO nick.uklinux.net) (194.247.51.141) by sourceware.org with SMTP; 11 Jul 2004 22:49:22 -0000 Received: by nick.uklinux.net (Postfix, from userid 501) id 984A775FDF; Sun, 11 Jul 2004 22:49:57 +0100 (BST) From: Nick Roberts Message-ID: <16625.46597.86962.340302@nick.uklinux.net> Date: Sun, 11 Jul 2004 22:49:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrew Cagney Cc: Nick Roberts , Alain Magloire , Daniel Jacobowitz , gdb@sources.redhat.com Subject: Re: How does GDB/MI give the current frame In-Reply-To: <40EDC76F.2070809@gnu.org> References: <40DE2D1B.4070003@gnu.org> <200406302047.QAA29956@smtp.ott.qnx.com> <16613.39781.921538.192414@nick.uklinux.net> <40EDC76F.2070809@gnu.org> X-SW-Source: 2004-07/txt/msg00102.txt.bz2 > > > > -> -interpreter cli "up" > > > > <- ~"info on new frame..." > > > > <- *select-frame,... > > > > <- done > > Note that the interpreter case is key, it lets the GUI respond to > operations on the command line. On my gdb, -interpreter-exec cli "up" gives: ^error,msg="mi_cmd_interpreter_exec: could not find interpreter \"cli\"" (gdb) I'm still lost here. > > There would still be problems with displaying the values of variables. > > Neither variable objects or the CLI command, display, seem to take > > notice of the thread number. > > ``bug'' in current MI protocol. How would something like: > > -thread 2 - > ^done > -thread 2 -frame 3 - > -frame 3 - > ^done Or values could be printed for all threads: -var-evaluate-expression var1 ^done,values=[{thread-id="0",value="0"},{thread-id="1",value="4"},...] and likewise for other mi commands. This would have the disadvantage of breaking existing behaviour but I imagine a user might want to see the value of a variable across all threads and would not wish to create a variable object for each thread. Nick