From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28049 invoked by alias); 20 Feb 2004 18:45:42 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 28028 invoked from network); 20 Feb 2004 18:45:41 -0000 Received: from unknown (HELO localhost.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 20 Feb 2004 18:45:41 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 455522B92; Fri, 20 Feb 2004 13:45:40 -0500 (EST) Message-ID: <403655D4.1020102@gnu.org> Date: Fri, 20 Feb 2004 18:45:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Elena Zannoni , David Carlton , gdb@sources.redhat.com Subject: Re: Huge slowdown since 6.0 References: <20040218210927.GA16641@nevyn.them.org> <20040220050905.GA15209@nevyn.them.org> <16438.14300.323849.306261@localhost.redhat.com> <40363D78.9080708@gnu.org> <16438.18096.205403.553354@localhost.redhat.com> <40364CF2.5020704@gnu.org> <20040220182411.GA14238@nevyn.them.org> In-Reply-To: <20040220182411.GA14238@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-02/txt/msg00292.txt.bz2 > On Fri, Feb 20, 2004 at 01:07:46PM -0500, Andrew Cagney wrote: > >>> Even if we start out with on-demand, it should work better. Given: >>> >>> $ gdb foo >>> (gdb) break main >>> (gdb) run >>> >>> why is GDB loading glibc's symbols? > > > Main might be a function defined in a shared library. Even if we found > a definition in the executable, it might be a PLT loading slot. KDE > on i386 will demonstrate this exact behavior. It's been suggested to me that we should create a hacked gdb that records all commands et.al. to a file, and then offers to send them to us. That way we know what is, rather than what might be. If we knew for instance that only 10% of users set breakpoints outside of the main executible, then we'd also know that we were frustrating 90% of users by making them sit around waiting for needless symbol table reads :-( On the other hand, if we knew that the first thing people did was: (gdb) break we'd have an entirely different problem. Andrew