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 rust/29202] New: [gdb/rust] Running selftest rust-lex. Self test failed: Converting character sets: Invalid argument. Date: Tue, 31 May 2022 08:58:53 +0000 [thread overview] Message-ID: <bug-29202-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29202 Bug ID: 29202 Summary: [gdb/rust] Running selftest rust-lex. Self test failed: Converting character sets: Invalid argument. Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Here ( https://builder.sourceware.org/buildbot/#/builders/98/builds/10 ) we have: ... Running selftest rust-lex. Self test failed: Converting character sets: Invalid argument. ... Ran 147 unit tests, 1 failed (gdb) PASS: gdb.gdb/unittest.exp: no executable loaded: maintenance selftest, ran some tests FAIL: gdb.gdb/unittest.exp: no executable loaded: maintenance selftest, failed none ... I managed to reproduce this in a container helpfully set up by Martin Liška. The root cause turned out to be this call failing: ... (gdb) fin Run till exit from #0 0x00007f0c2e11668e in iconv_open () from /lib64/libc.so.6 iconv_wrapper::iconv_wrapper (from=0x11946e0 "ANSI_X3.4-1968", to=0x96de99 "UTF-32LE", this=<synthetic pointer>) at ../../gdb/charset.c:476 ... because the support for UTF-32LE was not installed. Adding the package glibc-locale made the test pass. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-05-31 8:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-31 8:58 vries at gcc dot gnu.org [this message] 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 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@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).