From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10544 invoked by alias); 19 Apr 2002 07:26:58 -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 10431 invoked from network); 19 Apr 2002 07:26:52 -0000 Received: from unknown (HELO freya.inter.net.il) (192.114.186.14) by sources.redhat.com with SMTP; 19 Apr 2002 07:26:52 -0000 Received: from zaretsky ([80.230.2.40]) by freya.inter.net.il (Mirapoint Messaging Server MOS 2.9.3.2) with ESMTP id BII89847; Fri, 19 Apr 2002 10:26:35 +0300 (IDT) Date: Fri, 19 Apr 2002 00:26:00 -0000 From: "Eli Zaretskii" To: ac131313@cygnus.com Message-Id: <7872-Fri19Apr2002101810+0300-eliz@is.elta.co.il> CC: drow@mvista.com, gdb@sources.redhat.com In-reply-to: <3CBF6BEF.2050003@cygnus.com> (message from Andrew Cagney on Thu, 18 Apr 2002 20:59:27 -0400) Subject: Re: Multi-arch only GDB 6.0 .... Reply-to: Eli Zaretskii References: <3CBF600D.8090205@cygnus.com> <20020418201548.A14027@nevyn.them.org> <3CBF6BEF.2050003@cygnus.com> X-SW-Source: 2002-04/txt/msg00325.txt.bz2 > Date: Thu, 18 Apr 2002 20:59:27 -0400 > From: Andrew Cagney > > Why should GDB 6.0 retain support non-multi-arch targets? If someone > needs to debug a non-multi-arch target they can download GDB 5.x. That's not a practical solution, I'm afraid. Old versions aren't maintained, so they suffer bitrot very quickly as the world moves on. For example, by the time GDB 6.0 is released, GDB 5.x might not even compile with the then current development tools. Are we going to tell users of non-multi-arched targets to install old versions of compilers, libraries, headers, etc.? So in general, I'd advise against such a ``revolutionary'' approach. In practice, it tends to be too harsh to users, IMHO.