From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10097 invoked by alias); 11 Jan 2012 20:26:47 -0000 Received: (qmail 9988 invoked by uid 22791); 11 Jan 2012 20:26:46 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Jan 2012 20:26:35 +0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/13511] 'info variable' and 'info functions' very slow and memory cosuming Date: Wed, 11 Jan 2012 20:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at google dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2012-q1/txt/msg00061.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=13511 dje at google dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ccoutant at google dot com, | |dje at google dot com --- Comment #1 from dje at google dot com 2012-01-11 20:25:51 UTC --- gdb does full symtab expansion here which will use a lot of debug info. One thought is to have enough information to be able to avoid that. E.g., could .gdb_index include enough info to avoid having to do full symtab expansion? [that also has problems, but "info var|fun|type" is common enough that triggering an explosion of debug info reading is annoying and worth avoiding] [and similarly for psymtabs, as well as maybe enhancing pubnames/pubtypes] Another thought is to be more selective with debug info reading. Is it possible to read only the parts of the CU (dwarf-speak) that we need? Another thought is to throw out the info as we're finished using it, perhaps guided by various parameters. [we'll have to read it again, but that's preferable to bringing a machine to a crawl] -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.