This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug symtab/14002] New: big cpu/mem hog on large c++ applications.


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]