From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2438 invoked by alias); 17 Feb 2004 19:00:58 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 2431 invoked from network); 17 Feb 2004 19:00:56 -0000 Received: from unknown (HELO localhost.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 17 Feb 2004 19:00:56 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 2E8622B92; Tue, 17 Feb 2004 14:00:55 -0500 (EST) Message-ID: <403264E6.2010807@gnu.org> Date: Tue, 17 Feb 2004 19:00:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 MIME-Version: 1.0 To: Bob Rossi Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa:doco] Zap mi1 reference References: <402D2DF2.8030001@gnu.org> <20040213203704.GA654@white> <403151D2.1060908@gnu.org> <20040216234151.GA4921@white> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-02/txt/msg00474.txt.bz2 > If I was to write an MI module for libtgdb, do you see that working for > only gdb 6.0? Would I then have to write a MI2 module for 6.1? I would > hope that my MI1 library would work with both GDB 6.0,6.1. Is this a > quality the MI protocol is going to sustain? and that an MI2 module > would only allow for more functionality, or more of something. > > >> - using frame ID's with varobj >> - N:M breakpoints >> will impact significantly on the MI interface. > > > Will this break all MI1 front end clients? To turn the problem around, clients that don't exploit the new mechanisms are, by definition, already broken :-/ For instance without a frame ID it isn't possible for varobj to correctly identify a frame. This means that when your existing code tries to debug frameless i386 backtraces it's going to fail in wierd and wonderful ways (typically by selecting the wrong frame). Only by by identifying frames using a frame ID will your code be able to work robustly. Andrew