From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9F5313864877; Mon, 23 Nov 2020 11:29:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9F5313864877 From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/26933] New: [gdb/symtab] Too many: "warning: (Internal error: pc $hex in read in psymtab, but not in symtab.)" Date: Mon, 23 Nov 2020 11:29:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2020 11:29:27 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26933 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 --=20 You are receiving this mail because: You are on the CC list for the bug.=