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/17001] New: Only keep last N recently referenced symtabs


https://sourceware.org/bugzilla/show_bug.cgi?id=17001

            Bug ID: 17001
           Summary: Only keep last N recently referenced symtabs
           Product: gdb
           Version: HEAD
            Status: NEW
          Keywords: performance
          Severity: enhancement
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

Some of my benchmarks grow gdb's memory usage to 10s of GB, bringing my test
machine to a crawl.  Some of them even bring it to the point where xmalloc
aborts due to out of memory (I have 32GB mem and 32GB swap on my test machine).

To avoid this gdb could change how symtabs are stored so that we could only
keep the last N recently referenced one. Or gdb could keep track of its memory
usage (maybe as a percent of total memory?) and starting discarding symtabs
when above some limit.  Or both.

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