From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6340 invoked by alias); 5 Oct 2004 09:10: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 6318 invoked from network); 5 Oct 2004 09:10:17 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 5 Oct 2004 09:10:17 -0000 Received: from zaretski ([80.230.155.207]) by legolas.inter.net.il (MOS 3.5.3-GR) with ESMTP id CTE21276 (AUTH halo1); Tue, 5 Oct 2004 11:10:08 +0200 (IST) Date: Tue, 05 Oct 2004 09:18:00 -0000 From: "Eli Zaretskii" To: Fabian Cenedese Message-ID: <01c4aaba$Blat.v2.2.2$d1019f80@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: gdb@sources.redhat.com In-reply-to: <5.2.0.9.1.20041005085052.01ce8e18@NT_SERVER> (message from Fabian Cenedese on Tue, 05 Oct 2004 08:59:32 +0200) Subject: Re: GDB/MI snapshots between major release's Reply-to: Eli Zaretskii References: <20041004205357.1FBCD502AB6@stray.canids> <20041003163918.GB7030@white> <01c4a9ce$Blat.v2.2.2$d01969a0@zahav.net.il> <20041004131906.GB8121@white> <20041004145921.BAC77502AB6@stray.canids> <20041004154928.GE8121@white> <20041004160455.DD23A502AB6@stray.canids> <20041004164803.GG8121@white> <20041004181201.9A8E9502AB6@stray.canids> <20041004183145.GH8121@white> <20041004205357.1FBCD502AB6@stray.canids> <5.2.0.9.1.20041005085052.01ce8e18@NT_SERVER> X-SW-Source: 2004-10/txt/msg00073.txt.bz2 > Date: Tue, 05 Oct 2004 08:59:32 +0200 > From: Fabian Cenedese > > One thing that could be added is that -i mi doesn't mean the last > one (like mi2 now) but the last official one. So if there will be a > mi3 in progress mi will still select mi2. Like that you will always > be using the last stable protocol. And others can work with the > development version by calling -i mi3. But that won't solve your > problem of knowing what mi version the last stable really is. Knowing which MI version is the last stable one is important, but it's a separate issue. Do we all agree that for official GDB releases the problem of MI versions is solved by the features that we already have, or do someone think that a feature that reports supported MI versions is still needed even for the official releases? Let's solve the situation with official releases first, and get to the development versions later. As for the problem with development versions, I think it's part of a larger problem: how can one know that a certain snapshot is stable enough to make it available to users? The stability of MI is a relatively small aspect of this larger problem, and there's always the solution suggested by Jason (I think): use the latest stable version of MI, the one released with the last official GDB version.