public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/29315] Completion warning: could not convert ... from the host encoding (ANSI_X3.4-1968) to UTF-32
Date: Sat, 03 Sep 2022 21:15:56 +0000	[thread overview]
Message-ID: <bug-29315-4717-WKFk1k76sZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29315-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Patrick Monnerat from comment #1)

> In the mingw context, current code conditionals cause libiconv to be
> replaced by a minimal phony_iconv that does not support such conversions.
> These conditionals were implemented to make sure libiconv implements UTF32
> and fail on mingw because the wchar_t is 16-bit wide and the installed
> libiconv is not the Bruno Haible's one. See PHONY_ICONV in gdb/gdb_wchar.h.

Are there any defines in the mingw libiconv headers that could be used
to detect this situation?  E.g., for Haible's we use _LIBICONV_VERSION.
Anyway I'd be curious to know exactly which situation makes gdb decide
not to use iconv in your configuration.

> @maciej: is your context similar (no Haible's libiconv or too old and no
> ISO-10646 support) ?

Ideally this path shouldn't even be taken.  However it may be hard
to avoid due to a combination of factors including multi-language searches.

One question I had is whether the required iconv converters are installed.
It sounds like he's using glibc...

> @tom: as you're the commit's author, what is your opinion ?

In the past we couldn't assume host iconv was any good.  Solaris in
particular was broken (I forget how).  I suppose I'm ok with changing
this decision though it might be good to find out how Solaris is doing.

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

  parent reply	other threads:[~2022-09-03 21:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 15:09 [Bug cli/29315] New: " macro at orcam dot me.uk
2022-09-03 18:56 ` [Bug cli/29315] " patrick at monnerat dot net
2022-09-03 21:15 ` tromey at sourceware dot org [this message]
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-WKFk1k76sZ@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).