From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20771 invoked by alias); 9 Jul 2004 11:34:19 -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 20757 invoked from network); 9 Jul 2004 11:34:17 -0000 Received: from unknown (HELO lakermmtao01.cox.net) (68.230.240.38) by sourceware.org with SMTP; 9 Jul 2004 11:34:17 -0000 Received: from white ([68.9.64.121]) by lakermmtao01.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040709113417.YYLS29186.lakermmtao01.cox.net@white> for ; Fri, 9 Jul 2004 07:34:17 -0400 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1Bitdw-0001Ii-00 for ; Fri, 09 Jul 2004 07:34:16 -0400 Date: Fri, 09 Jul 2004 11:34:00 -0000 From: Bob Rossi To: gdb@sources.redhat.com Subject: bob@brasko.net: Re: MI level command Message-ID: <20040709113416.GA4979@white> Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-SW-Source: 2004-07/txt/msg00089.txt.bz2 On Thu, Jul 08, 2004 at 07:33:17PM -0400, Alain Magloire wrote: > Yellow > > > Scenario: We want to know wich level of MI that we are currently working in. > This can allow to adjust what MI command to use and how to parse them. > > Problems: No such command in MI and no GDB variable that we can test via -gdb-show. > The version of gdb > gdb --version > show different things in different distributions, sometimes it is a number based on date > etc ... > > So would a patch implementing > > -gdb-mi-level > ^done,level=1 > > be a good thing ? I like this idea a lot. I will need it when I start getting more work done on TGDB. However, there is another DRY problem. What functions act which way for which level? Basically, should every front end understand that -file-list-exec-source-files outputs just the files for level 1 but it also outputs the libraries the files belong to in level2? One solution could be, for every MI function, we could generate a unique key. For example, mi1-file-list-exec-source-files, mi2-file-list-exec-source-files, ... This key would tell the front end to use that particular parsing function when checking the output of -file-list-exec-source-files. Is this to wacky? Thanks, Bob Rossi