This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/15035] New: Excessive symtab expansion setting abreakpoint on foo::bar.
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 18 Jan 2013 19:43:06 +0000
- Subject: [Bug symtab/15035] New: Excessive symtab expansion setting abreakpoint on foo::bar.
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15035
Bug #: 15035
Summary: Excessive symtab expansion setting a breakpoint on
foo::bar.
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: symtab
AssignedTo: unassigned@sourceware.org
ReportedBy: dje@google.com
Classification: Unclassified
I haven't looked into the psymtab side, but when using .gdb_index and doing
(gdb) b (anonymous namespace)::foo
gdb will first expand every CU/TU (dwarf) that defines anonymous namespace, and
only after that will it look for foo.
However, the symbol table in .gdb_index has an entry for (anonymous
namespace)::foo. The data is there to tell gdb precisely which CUs to expand.
Seems like the index isn't being fully utilitized here.
In a large app there could be 2k such CUs (or more), and setting a breakpoint
takes way too long (long enough that I give up after a minute and haven't put
in the effort to compute the actual number).
--
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.