From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 982 invoked by alias); 3 Oct 2004 18:00:32 -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 972 invoked from network); 3 Oct 2004 18:00:31 -0000 Received: from unknown (HELO epic.mail.pas.earthlink.net) (207.217.120.181) by sourceware.org with SMTP; 3 Oct 2004 18:00:31 -0000 Received: from ip216-26-76-19.dsl.du.teleport.com ([216.26.76.19] helo=stray.canids) by epic.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1CEAes-0005aW-00 for gdb@sources.redhat.com; Sun, 03 Oct 2004 11:00:31 -0700 Received: from stray.canids (localhost.localdomain [127.0.0.1]) by stray.canids (Postfix) with ESMTP id 6B230502AB6 for ; Sun, 3 Oct 2004 11:00:30 -0700 (PDT) From: Felix Lee To: GDB Subject: Re: GDB/MI snapshots between major release's References: <20041003163918.GB7030@white> In-Reply-To: <20041003163918.GB7030@white> on Sun, 03 Oct 2004 12:39:18 EDT from Bob Rossi Date: Sun, 03 Oct 2004 18:36:00 -0000 Message-Id: <20041003180030.6B230502AB6@stray.canids> X-SW-Source: 2004-10/txt/msg00030.txt.bz2 Bob Rossi : > How should front end developers deal with snapshots of GDB, that are > taken between major versions of GDB. Several distributions I think you're overthinking this. if some version of gdb doesn't fulfill the compatibility guarantee, then it's a bug in gdb, and it shouldn't be hard to have the user install a gdb version without the bug. at worst, you can supply your own version of gdb. few things depend on specific gdb version. it's not a big deal to have multiple gdb versions installed. source code availability means you don't have to wait for the gdb cabal to fix it, and the cabal is generally eager to take reasonable bugfixes, which solves the long-term problem. --