public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/14002] New: big cpu/mem hog on large c++ applications.
Date: Fri, 20 Apr 2012 14:40:00 -0000	[thread overview]
Message-ID: <bug-14002-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=14002

             Bug #: 14002
           Summary: big cpu/mem hog on large c++ applications.
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: critical
          Priority: P2
         Component: symtab
        AssignedTo: unassigned@sourceware.org
        ReportedBy: pluto@agmk.net
    Classification: Unclassified


hi,

i have a large c++ application (2.9GB of shared objects, 600MB of static
archives used in shared objects). on isolated part of sources a single
'next' call takes ~3 minutes and increases memory usage from ~500M to ~3G
while previous gdb-7.3.1 needs only 2..3 seconds and increases memory usage
from ~400M to ~550MB.

7bd518fd9738c50a5197af2b184acd97e4d4df40 is the first bad commit

commit 7bd518fd9738c50a5197af2b184acd97e4d4df40
Author: Tom Tromey <tromey@redhat.com>
Date:   Mon Jul 11 17:17:25 2011 +0000

        * dwarf2read.c (handle_DW_AT_stmt_list): New function.
        (read_file_scope, read_type_unit_scope): Use it.


link to gdb mailinglist discussion:
http://sourceware.org/ml/gdb/2012-03/msg00096.html

-- 
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.


             reply	other threads:[~2012-04-20 14:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20 14:40 pluto at agmk dot net [this message]
2012-04-20 14:42 ` [Bug symtab/14002] " pluto at agmk dot net
2012-04-24 20:00 ` pluto at agmk dot net
2012-04-28 16:51 ` pluto at agmk dot net
2012-05-21  1:21 ` dje at google dot com
2012-07-08 22:59 ` loic.yhuel at gmail dot com
2012-11-13 22:40 ` dje at google dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14002-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).