public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "patrick at monnerat dot net" <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: Sun, 01 Oct 2023 17:59:27 +0000 [thread overview] Message-ID: <bug-29315-4717-gxpg8s4jn7@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 #6 from Patrick Monnerat <patrick at monnerat dot net> --- > I can make one available to you if that would help! Thank you very much for the proposal, but I don't think I will investigate more about it as this brings me very far from the Insight GUI, the initial simple patch I submitted being not welcomed. Since then, I successfully use the mingw workaround I suggested in comment 4. > I am still seeing this issue in gdb 13.2 on OmniOS (illumos) and have heard about it on OpenIndiana and Oracle Solaris 11.4 as well. This comforts me into thinking it should be resolved by someone who masters these OSes. Thanks a lot anyway! -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-01 17:59 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 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 [this message] 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-gxpg8s4jn7@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).