public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31853] GDB's use of iconv does not work with macOS Sonoma
Date: Tue, 11 Jun 2024 10:30:11 +0000	[thread overview]
Message-ID: <bug-31853-4717-XvMOt0OKpM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31853-4717@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Ciaran Woodward <ciaran@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=bb2981798f54e6eb30e46fb11cda2ca49561ffd3

commit bb2981798f54e6eb30e46fb11cda2ca49561ffd3
Author: Ciaran Woodward <ciaranwoodward@xmos.com>
Date:   Mon Jun 10 16:52:37 2024 +0100

    Fix printing strings on macOS Sonoma

    On macOS sonoma, printing a string would only print the first
    character. For instance, if there was a 'const char *s = "foobar"',
    then the 'print s' command would print '$1 = "f"' rather than the
    expected '$1 = "foobar"'.

    It seems that this is due to Apple silently replacing the version
    of libiconv they ship with the OS to one which silently fails to
    handle the 'outbytesleft' parameter correctly when using 'wchar_t'
    as a target encoding.

    This specifically causes issues when using iterating through a
    string as wchar_iterator does.

    This bug is visible even if you build for an old version of macOS,
    but then run on Sonoma. Therefore this fix in the code applies
    generally to macOS, and not specific to building on Sonoma. Building
    for an older version and expecting forwards compatibility is a
    common situation on macOS.

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

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

  parent reply	other threads:[~2024-06-11 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 15:10 [Bug gdb/31853] New: " ciaranwoodward at xmos dot com
2024-06-06 15:10 ` [Bug gdb/31853] " ciaranwoodward at xmos dot com
2024-06-06 15:25 ` ciaranwoodward at xmos dot com
2024-06-07 15:30 ` tromey at sourceware dot org
2024-06-07 16:18 ` ciaranwoodward at xmos dot com
2024-06-07 21:32 ` tromey at sourceware dot org
2024-06-10 16:16 ` ciaranwoodward at xmos dot com
2024-06-11 10:30 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-11 15:08 ` tromey at sourceware dot org
2024-06-12 10:21 ` cvs-commit at gcc dot gnu.org
2024-06-12 12:39 ` tromey at sourceware dot 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-31853-4717-XvMOt0OKpM@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).