From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29420 invoked by alias); 16 Jan 2009 03:47:17 -0000 Received: (qmail 29412 invoked by uid 22791); 16 Jan 2009 03:47:16 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Jan 2009 03:46:32 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E29BD2A96DF for ; Thu, 15 Jan 2009 22:46:30 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VE0xmtm4UlKN for ; Thu, 15 Jan 2009 22:46:30 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 6FF052A96DE for ; Thu, 15 Jan 2009 22:46:30 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 81A69E7ACD; Fri, 16 Jan 2009 07:46:23 +0400 (RET) Date: Fri, 16 Jan 2009 03:47:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: Re: Discussing the next GDB release (GDB 7.0?) Message-ID: <20090116034623.GJ31296@adacore.com> References: <20090115034552.GF24105@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090115034552.GF24105@adacore.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-01/txt/msg00087.txt.bz2 > Anything else that you'd like to be put on the list for > this release? Tom suggested PR/9711: Quadratic slowdown in backtrace command. I added to the list because it is a regression compared to 6.8, but the example given shows the heavy slowdown only with a very large number of frames. I wonder if this can happen with a more typical number of frames - I suspect that Paul (the submitter) probably hit the problem in a real situation before coming up with this reduced example... Daniel, it looks like you started looking into it at some point. Is this issue still on your list? What do you think about having it fixed for the next release? -- Joel