)]}'
{
  "commit": "c9f1e0dfc8f02a7772aa383cc305d9049075d1d8",
  "tree": "2a18e0cbf9bd23a669f6e5ba5c4280d44f537b9f",
  "parents": [
    "06bfdc6e5ee0745877ef941f50f680d342b5c585"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Fri Dec 22 11:48:54 2023 +0000"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Thu Jan 04 09:24:18 2024 +0000"
  },
  "message": "gdb: don\u0027t try to style content in error calls\n\nWhile working on a later commit in this series I realised that the\nerror() function doesn\u0027t support output styling.  Due to the way that\noutput from error() calls is passed around within the exception\nobject and often combined with other output, it\u0027s not immediately\nobvious to me if we should be trying to support styling in this\ncontext or not.\n\nOn inspection, I found one place in GDB where we apparently try to\napply styling within the error() output (in procfs.c).  I suspect this\nerror() call might not be tested.\n\nRather than try to implement styling in the error() output, right now\nI\u0027m proposing to just remove the attempt to style error() output.\n\nThis doesn\u0027t mean that someone shouldn\u0027t add error() styling in the\nfuture, but right now, I\u0027m not planning to do that, I just wanted to\nfix this in passing.\n\nApproved-By: John Baldwin \u003cjhb@FreeBSD.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1410bbc0d7d652a398ca379befb51dffa813026d",
      "old_mode": 33188,
      "old_path": "gdb/procfs.c",
      "new_id": "0eafc2eddcc146fd0fce37094969bb410a214a7a",
      "new_mode": 33188,
      "new_path": "gdb/procfs.c"
    }
  ]
}