public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "macro at orcam dot me.uk" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/29315] New: Completion warning: could not convert ... from the host encoding (ANSI_X3.4-1968) to UTF-32
Date: Fri, 01 Jul 2022 15:09:28 +0000	[thread overview]
Message-ID: <bug-29315-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29315
           Summary: Completion warning: could not convert ... from the
                    host encoding (ANSI_X3.4-1968) to UTF-32
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: macro at orcam dot me.uk
  Target Milestone: ---

Following the breakage from PR cli/29314, when debugging `cc1' from GCC
12, which has a huge number of template class functions, e.g.:

hash_table<action_record_hasher, false, xcallocator>::expand()
hash_table<action_record_hasher, false,
xcallocator>::find_slot_with_hash(action_record* const&, unsigned int,
insert_option)
hash_table<action_record_hasher, false, xcallocator>::~hash_table()
hash_table<addr_hasher, false, xcallocator>::expand()
[1100+ entries follow]

in some cases if you try to continue completing an incorrect completion
produced, then a warning is issued as follows:

(gdb) break hash_tab le<<Tab>
(gdb) break hash_tab le<warning: could not convert 'hash_tab le<' from the host
encoding (ANSI_X3.4-1968) to UTF-32.
This normally should not happen, please file a bug report.

and GDB hangs for a couple of minutes before silently returning to the 
prompt (i.e. it's not shown unless e.g. ^U is entered at this point).

This actually asks for a bug report, so here you go.

I can reproduce it with:

$ gdb /path/to/cc1

(having compiled `cc1' with debug info of course) on a native
RISC-V/Linux system, specifically the SiFive Freedom U SDK Linux
distribution provided with the HiFive Unmatched development system:

$ cat /etc/os-release
ID=nodistro
NAME="FreedomUSDK"
VERSION="2021.03.01 (2021March)"
VERSION_ID=2021.03.01
PRETTY_NAME="FreedomUSDK 2021.03.01 (2021March)"
$ 

I have no idea why a warning pops up from gdb/ada-lang.c for an
executable that contains no Ada code:

(gdb) show language
The current source language is "auto; currently c++".
(gdb) 

I may be able to provide further details later.

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

             reply	other threads:[~2022-07-01 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 15:09 macro at orcam dot me.uk [this message]
2022-09-03 18:56 ` [Bug cli/29315] " patrick at monnerat dot net
2022-09-03 21:15 ` tromey at sourceware dot org
2022-09-03 23:29 ` patrick at monnerat dot net
2022-09-06 13:03 ` patrick at monnerat dot net
2023-10-01 17:11 ` robert at robertdfrench dot me
2023-10-01 17:28 ` pjfloyd at wanadoo dot fr
2023-10-01 17:59 ` patrick at monnerat dot net
2023-10-05  8:55 ` pjfloyd at wanadoo dot fr

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-29315-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: 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).