[Bug symtab/17603] New: gdb needs a mode to not use minsyms, it hides psymtab/symtab bugs

[Bug symtab/17603] New: gdb needs a mode to not use minsyms, it hides psymtab/symtab bugs

[dje at google dot com]

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

            Bug ID: 17603
           Summary: gdb needs a mode to not use minsyms, it hides
                    psymtab/symtab bugs
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

gdb needs a mode to tell it to not use minsyms, at least for certain kinds of
lookup during testing.

PR 17602 is an example where things work, but only because minsyms come to the
rescue.

This is not the first time I've seen gdb work but only because one lookup fails
(where it shouldn't have) and then another kind of lookup succeeds and from the
user's perspective (and the testsuite's!) things are OK.  But they are not!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug symtab/17603] gdb needs a mode to not use minsyms, it hides psymtab/symtab bugs

[dje at google dot com]

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

--- Comment #1 from dje at google dot com ---
Another possibility is have a mode where we don't demangle minsyms.
Need to collect some perf data regardless: In my monster benchmark, 12 of 13
seconds of gdb startup time is reading ELF symbols.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug symtab/17603] gdb needs a mode to not use minsyms, it hides psymtab/symtab bugs

[dje at google dot com]

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

--- Comment #2 from dje at google dot com ---
Note: PR 17604 addresses the performance cost of demangling minsyms.

-- 
You are receiving this mail because:
You are on the CC list for the bug.