[Bug symtab/26933] New: [gdb/symtab] Too many: "warning: (Internal error: pc $hex in read in psymtab, but not in symtab.)"

[Bug symtab/26933] New: [gdb/symtab] Too many: "warning: (Internal error: pc $hex in read in psymtab, but not in symtab.)"

[vries at gcc dot gnu.org]

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

            Bug ID: 26933
           Summary: [gdb/symtab] Too many: "warning: (Internal error: pc
                    $hex in read in psymtab, but not in symtab.)"
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: minor
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

While porting the openSUSE gdb package to 10.1, I ran into:
...
Running
/home/abuild/rpmbuild/BUILD/gdb-10.1/gdb/testsuite/gdb.base/morestack.exp ...
PASS: gdb.base/morestack.exp: continue
ERROR: internal buffer is full.
UNRESOLVED: gdb.base/morestack.exp: up 3000
...
for unix/-m32/-fPIE/-pie.

In more detail:
...
(gdb) PASS: gdb.base/morestack.exp: continue
up 3000^M
warning: (Internal error: pc 0x56555dc8 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555dc9 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555dc9 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555d62 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555dc8 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555dc8 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555dc8 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555dc8 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555dc9 in read in psymtab, but not in
symtab.)^M
  ...
warning: (Internal error: pc 0x56555dc9 in read in psymtab, but not in
symtab.)^M
^M
warning: (Internal error: pc 0x56555d62 in read in psymtab, but not in
symtab.)^M
^M
waERROR: internal buffer is full.
UNRESOLVED: gdb.base/morestack.exp: up 3000
...

This doesn't reproduce for a normal master build, so I think this is fixed.

But:
- the wording is strange: is it a warning or internal error?
- flooding the user with warnings like this is not helpful either

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

[Bug symtab/26933] [gdb/symtab] Too many: "warning: (Internal error: pc $hex in read in psymtab, but not in symtab.)"

[vries at gcc dot gnu.org]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> 
> This doesn't reproduce for a normal master build, so I think this is fixed.

Actually, no.

The test-case is passing, but the warnings are there, just not in the amount to
trigger ERROR/UNRESOLVED.

Filed PR26935 - "[gdb/testsuite] Using gold in gdb.base/morestack.exp causes
incorrect debug info" for the actual problem that makes the warning trigger.

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