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 testsuite/29202] [gdb/rust] Running selftest rust-lex. Self test failed: Converting character sets: Invalid argument. Date: Tue, 31 May 2022 09:24:04 +0000 [thread overview] Message-ID: <bug-29202-4717-LXbio5ys14@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29202-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29202 --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- Hmm, in ada-lang.c we have: ... try { convert_between_encodings (host_charset (), HOST_UTF32, (const gdb_byte *) name.data (), name.length (), 1, &storage, translit_none); } catch (const gdb_exception &) { if (throw_on_error) throw; static bool warned = false; /* Converting to UTF-32 shouldn't fail, so if it doesn't, we might like to know why. */ if (!warned) { { warned = true; warning (_("could not convert '%s' from the host encoding (%s) to UTF-32.\n" "This normally should not happen, please file a bug report."), gdb::to_string (name).c_str (), host_charset ()); } ... I suppose we could use something similar. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-31 9:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-31 8:58 [Bug rust/29202] New: " vries at gcc dot gnu.org 2022-05-31 8:59 ` [Bug testsuite/29202] " vries at gcc dot gnu.org 2022-05-31 9:03 ` vries at gcc dot gnu.org 2022-05-31 9:24 ` vries at gcc dot gnu.org [this message] 2022-06-01 15:44 ` tromey at sourceware dot org 2022-06-03 10:39 ` vries at gcc dot gnu.org 2022-06-03 10:53 ` mark at klomp dot org 2022-06-03 11:02 ` mark at klomp dot org 2022-06-03 11:12 ` mark at klomp dot org 2022-06-07 12:18 ` vries at gcc dot gnu.org
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-29202-4717-LXbio5ys14@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: linkBe 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).