public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/26933] [gdb/symtab] Too many: "warning: (Internal error: pc $hex in read in psymtab, but not in symtab.)"
Date: Tue, 24 Nov 2020 12:43:17 +0000	[thread overview]
Message-ID: <bug-26933-4717-5Y5Uw0Ol8V@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26933-4717@http.sourceware.org/bugzilla/>

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.

      reply	other threads:[~2020-11-24 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 11:29 [Bug symtab/26933] New: " vries at gcc dot gnu.org
2020-11-24 12:43 ` vries at gcc dot gnu.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-26933-4717-5Y5Uw0Ol8V@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).