This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/13511] 'info variable' and 'info functions' very slowand memory cosuming
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 11 Jan 2012 20:25:51 +0000
- Subject: [Bug symtab/13511] 'info variable' and 'info functions' very slowand memory cosuming
- Auto-submitted: auto-generated
- References: <bug-13511-4717@http.sourceware.org/bugzilla/>
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.