From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16962 invoked by alias); 20 Nov 2003 20:22:34 -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 16952 invoked from network); 20 Nov 2003 20:22:34 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 20 Nov 2003 20:22:34 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id hAKKMXH24457 for ; Thu, 20 Nov 2003 15:22:33 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id hAKKMVa27340; Thu, 20 Nov 2003 15:22:31 -0500 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id hAKKMUH24822; Thu, 20 Nov 2003 12:22:30 -0800 Message-ID: <3FBD2286.8030307@redhat.com> Date: Thu, 20 Nov 2003 20:22:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Will Cohen CC: gdb-patches@sources.redhat.com Subject: Re: Slow handling of C++ symbol names References: <3FBBDC27.50204@redhat.com> <3FBC217A.40105@redhat.com> <3FBCCF3C.5080703@redhat.com> In-Reply-To: <3FBCCF3C.5080703@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00429.txt.bz2 Will Cohen wrote: > Michael Snyder wrote: > >> Will Cohen wrote: >> >>> When debugging some C++ program with gdb (both versions 5.3 and 6.0) >>> it takes a long time to load the debugging information and get a >>> command-line prompt. The particular example that demonstrates this >>> problem is monotone (http://www.venge.net/monotone/) which makes use >>> of the boost libraries (http://www.boost.org/). gdb loading monotone >>> with the associated debugging information takes over 30 seconds to >>> get the initial command-line prompt on a 1.7GHz Athlon with 512MB or >>> DRAM. >> >> >> >> 30 seconds! Why, you young whipper-snapper... I remember when you >> used to have to go get a cup of coffee while gdb loaded symbols! ;-) >> Hell, sometimes you could go out and *buy* the coffee... > > > In the early 90's I did a port of GCC to the Gould NP1, a dual processor > machine (18MHz ECL multiboard processors) with a staggering 256MB of > RAM at Purdue University. Unfortunately, the machine was the main > machine for ALL the undergraduates. During the afternoons it was typical > to see gcc 1.40 take 3 hours to build when there were 70 or more people > on the machine. > > The process for gdb debugging monotone wouldn't fit in the NP1's 256MB > of memory. According to top SIZE is 265MB and RSS is 262MB. So maybe 30 > seconds for filling up a quarter gigabyte of memory isn't so bad. It would be bad if it were just copying from disk to memory, but it's not bad for parsing one database of that size into another with a completely different format.