)]}'
{
  "commit": "bb2981798f54e6eb30e46fb11cda2ca49561ffd3",
  "tree": "f163508b03b410e64420c18e52adbc9a980b1bc9",
  "parents": [
    "60e221e9b7fae5ff40b79b93bdbff909989c2bae"
  ],
  "author": {
    "name": "Ciaran Woodward",
    "email": "ciaranwoodward@xmos.com",
    "time": "Mon Jun 10 16:52:37 2024 +0100"
  },
  "committer": {
    "name": "Ciaran Woodward",
    "email": "ciaranwoodward@xmos.com",
    "time": "Tue Jun 11 11:28:51 2024 +0100"
  },
  "message": "Fix printing strings on macOS Sonoma\n\nOn macOS sonoma, printing a string would only print the first\ncharacter. For instance, if there was a \u0027const char *s \u003d \"foobar\"\u0027,\nthen the \u0027print s\u0027 command would print \u0027$1 \u003d \"f\"\u0027 rather than the\nexpected \u0027$1 \u003d \"foobar\"\u0027.\n\nIt seems that this is due to Apple silently replacing the version\nof libiconv they ship with the OS to one which silently fails to\nhandle the \u0027outbytesleft\u0027 parameter correctly when using \u0027wchar_t\u0027\nas a target encoding.\n\nThis specifically causes issues when using iterating through a\nstring as wchar_iterator does.\n\nThis bug is visible even if you build for an old version of macOS,\nbut then run on Sonoma. Therefore this fix in the code applies\ngenerally to macOS, and not specific to building on Sonoma. Building\nfor an older version and expecting forwards compatibility is a\ncommon situation on macOS.\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d31853\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8df00e4679f4486691b96e441e526408c0745080",
      "old_mode": 33188,
      "old_path": "gdb/gdb_wchar.h",
      "new_id": "909a0e4ac718e83a3a77281137a5b9d01e5dfa21",
      "new_mode": 33188,
      "new_path": "gdb/gdb_wchar.h"
    }
  ]
}