From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31994 invoked by alias); 7 Aug 2004 17:11:37 -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 31980 invoked from network); 7 Aug 2004 17:11:37 -0000 Received: from unknown (HELO aragorn.inter.net.il) (192.114.186.23) by sourceware.org with SMTP; 7 Aug 2004 17:11:37 -0000 Received: from zaretski ([80.230.155.37]) by aragorn.inter.net.il (MOS 3.4.6-GR) with ESMTP id ECE60613; Sat, 7 Aug 2004 20:11:31 +0300 (IDT) Date: Sat, 07 Aug 2004 17:11:00 -0000 From: "Eli Zaretskii" To: Andrew Cagney Message-Id: <9787-Sat07Aug2004200852+0300-eliz@gnu.org> CC: kettenis@chello.nl, gdb-patches@sources.redhat.com In-reply-to: <41150161.3000306@gnu.org> (message from Andrew Cagney on Sat, 07 Aug 2004 12:20:49 -0400) Subject: Re: [PATCH] Improve i386 prologue analyzer Reply-to: Eli Zaretskii References: <200408012158.i71LwpRw033840@elgar.kettenis.dyndns.org> <3405-Mon02Aug2004070159+0300-eliz@gnu.org> <410EAFBB.5080102@gnu.org> <2914-Tue03Aug2004065313+0300-eliz@gnu.org> <200408061933.i76JX3HJ008032@elgar.kettenis.dyndns.org> <4113EA3B.3000900@gnu.org> <2914-Sat07Aug2004183455+0300-eliz@gnu.org> <41150161.3000306@gnu.org> X-SW-Source: 2004-08/txt/msg00205.txt.bz2 > Date: Sat, 07 Aug 2004 12:20:49 -0400 > From: Andrew Cagney > > Mark wrote: > > > I'd really like this to get some exposure in HEAD before backporting > > it, but otherwise I do agree. Sure, but IMHO the change doesn't need too much testing more than it already got. Don't the developers use CVS HEAD most of the time? Don't they use it mostly on IA32 (GNU/Linux or otherwise) systems? If so, the patch is mostly tested. > Remember, at present MIPS is dead in the water. With backtraces misbehaving as they do now, I consider the x86 broken almost as badly as the MIPS. As I told before, because of that bug, I mistrusted GDB 6.1 to such a degree that I started to use GDB 5.x. > For how long should we delay pushing out a fix for that? A week or two won't do much harm, IMHO. But I doubt that we need even that much.