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/29205] Running selftest dw2_expand_symtabs_matching. warning: could not convert 'yfunc�' from the host encoding (UTF-8) to UTF-32
Date: Tue, 07 Jun 2022 13:05:53 +0000	[thread overview]
Message-ID: <bug-29205-4717-DEDAC08uTr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29205-4717@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 14134
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14134&action=edit
Tentative patch (downgrades warning to symbol_lookup_debug)

(In reply to Pedro Alves from comment #3)
> I think the "This normally should not happen, please file a bug report."
> warning it too strict -- I imagine it should be possible to pass such symbol
> names to the compiler by using escape codes.

This patch downgrades the warnings to symbol_lookup_debug messages.

WDYT?

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

      parent reply	other threads:[~2022-06-07 13:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 11:08 [Bug symtab/29205] New: " vries at gcc dot gnu.org
2022-05-31 11:11 ` [Bug symtab/29205] " vries at gcc dot gnu.org
2022-05-31 11:11 ` vries at gcc dot gnu.org
2022-05-31 11:25 ` vries at gcc dot gnu.org
2022-05-31 11:58 ` pedro at palves dot net
2022-05-31 12:06 ` vries at gcc dot gnu.org
2022-05-31 12:08 ` vries at gcc dot gnu.org
2022-05-31 12:23 ` vries at gcc dot gnu.org
2022-05-31 12:58 ` pedro at palves dot net
2022-06-07 13:05 ` 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-29205-4717-DEDAC08uTr@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).