From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16991 invoked by alias); 13 Oct 2004 20:33:28 -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 16982 invoked from network); 13 Oct 2004 20:33:26 -0000 Received: from unknown (HELO balder.inter.net.il) (192.114.186.15) by sourceware.org with SMTP; 13 Oct 2004 20:33:26 -0000 Received: from zaretski ([80.230.159.35]) by balder.inter.net.il (Mirapoint Messaging Server MOS 3.3.7-GR) with ESMTP id DUZ24829 (AUTH halo1); Wed, 13 Oct 2004 22:33:22 +0200 (IST) Date: Thu, 14 Oct 2004 07:10:00 -0000 From: "Eli Zaretskii" To: "'Bob Rossi'" Message-ID: <01c4b163$Blat.v2.2.2$7d934a60@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: gdb@sources.redhat.com In-reply-to: <20041013121412.GA22696@white> (message from 'Bob Rossi' on Wed, 13 Oct 2004 08:14:12 -0400) Subject: Re: probing GDB for MI versions Reply-to: Eli Zaretskii References: <20041007145511.GA14573@white> <200410071614.MAA19648@smtp.ott.qnx.com> <20041007224230.GA15177@white> <01c4ad12$Blat.v2.2.2$1796ec80@zahav.net.il> <20041009002901.GB16824@white> <20041013003135.GA22087@white> <01c4b0df$Blat.v2.2.2$e933d3e0@zahav.net.il> <20041013121412.GA22696@white> X-SW-Source: 2004-10/txt/msg00311.txt.bz2 > Date: Wed, 13 Oct 2004 08:14:12 -0400 > From: 'Bob Rossi' > Cc: gdb@sources.redhat.com > > > What's wrong with a simpler idea already suggested here: that GDB will > > output the MI version as part of the starting blurb when invoked with > > "-interpreter=mi" option? > > That method is fine if GDB supports only one stable MI protocol at a > time. However, I have been told that GDB will support multiple versions > of MI at a time. Yes, but Andrew just told you that GDB will most probably support at most 2 MI versions: the latest one and the one before that. So printing only the last version is okay, because if that version is not supported by your front end, you need only to check the previous version. Isn't that good enough? (Even if GDB does support more than 2 MI versions, you could still probe smaller versions until you either (1) find one that is okay with your front end, or (2) get GDB to fail because the MI version you requested is not supported. And if that is still not good enough, let's have GDB output a list of supported MI versions as part of its starting blurb, e.g. one version per line. Will that finally put this issue to rest?