From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25916 invoked by alias); 3 Jan 2009 19:21:28 -0000 Received: (qmail 25908 invoked by uid 22791); 3 Jan 2009 19:21:28 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_MX,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 03 Jan 2009 19:20:53 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n03JKmBF019066; Sat, 3 Jan 2009 14:20:48 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n03JKlb0005128; Sat, 3 Jan 2009 14:20:47 -0500 Received: from opsy.redhat.com (vpn-12-199.rdu.redhat.com [10.11.12.199]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n03JKkLW023352; Sat, 3 Jan 2009 14:20:47 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 10B443786BD; Sat, 3 Jan 2009 12:20:44 -0700 (MST) To: ppluzhnikov@google.com (Paul Pluzhnikov) Cc: gdb@sourceware.org Subject: Re: quadratic slowdown in 'where' command References: <20081104235737.CD4763A6B0B@localhost> From: Tom Tromey Reply-To: tromey@redhat.com Date: Sat, 03 Jan 2009 19:21:00 -0000 In-Reply-To: <20081104235737.CD4763A6B0B@localhost> (Paul Pluzhnikov's message of "Tue\, 4 Nov 2008 15\:57\:37 -0800 \(PST\)") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00006.txt.bz2 >>>>> "Paul" == Paul Pluzhnikov writes: Paul> While debugging something else, I noticed extreme slowdown of Paul> 'where' command for a deeply recursive stack trace, and was able Paul> to reproduce it on a small example (below). FWIW, I'm able to reproduce this as well. Paul> The results are also rather interesting: running 'where' by hand Paul> shows that GDB prints all levels except the last one rather fast, Paul> but then 'freezes' for a long time printing the last level. I wasn't able to reproduce this. That is, I ran the test a number of times, and sometimes I saw this effect, but sometimes I did not. Could you file this in bugzilla? Tom