From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32126 invoked by alias); 3 Nov 2011 16:43:58 -0000 Received: (qmail 32096 invoked by uid 22791); 3 Nov 2011 16:43:57 -0000 X-SWARE-Spam-Status: No, hits=-7.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 Nov 2011 16:43:23 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pA3GhMor026356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Nov 2011 12:43:22 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id pA3GhMZP011386; Thu, 3 Nov 2011 12:43:22 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id pA3GhK7q016538; Thu, 3 Nov 2011 12:43:21 -0400 From: Tom Tromey To: Jan Kratochvil Cc: Michael Eager , "gdb-patches\@sourceware.org" Subject: Re: SEGV in dwarf2read.c -- gdb-7.2 References: <4EB2BD58.3080003@eagerm.com> <20111103162026.GA12269@host1.jankratochvil.net> Date: Thu, 03 Nov 2011 16:43:00 -0000 In-Reply-To: <20111103162026.GA12269@host1.jankratochvil.net> (Jan Kratochvil's message of "Thu, 3 Nov 2011 17:20:26 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00078.txt.bz2 >>>>> "Jan" == Jan Kratochvil writes: Jan> I guess for performance reasons, the CU header read-in Jan> vs. load_full_comp_unit is a big difference. There are already Jan> some PRs (such as 12828 (a)) where GDB needlessly expands too many Jan> CUs "locking itself" by inacceptable performance. Does the CU cache serve a useful purpose these days? I wonder whether we could just remove it. Tom