)]}'
{
  "commit": "c541d53765bdea821b06b929ed5d13d00dc42f22",
  "tree": "635c6b52fb04be00f9ea7b8773b7c2934ae8eaca",
  "parents": [
    "679ad6e126868c462d8339eb837efb5a91a091af"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Mon Apr 22 09:33:06 2024 +0100"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Mon Apr 29 10:00:42 2024 +0100"
  },
  "message": "gdb/remote: fix qRcmd error handling\n\nThis commit:\n\n  commit 3623271997a5c0d79609aa6a1f35ef61b4469054\n  Date:   Tue Jan 30 15:55:47 2024 +0100\n\n      remote.c: Use packet_check_result\n\nIntroduced a bug in the error handling of the qRcmd packet.  Prior to\nthis commit if a packet had status PACKET_OK then, if the packet\ncontained the text \"OK\" we considered the packet handled.  But, if the\npacket contained any other content (that was not an error message)\nthen the content was printed to the user.\n\nAfter the above commit this was no longer the case, any non-error\npacket that didn\u0027t contain \"OK\" would be treated as an error.\n\nCurrently, gdbserver doesn\u0027t exercise this path so it\u0027s not possible\nto write a simple test for this case.  When gdbserver wishes to print\noutput it sends back an \u0027O\u0027 string output packet, these packets are\nhandled earlier in the process.  Then once gdbserver has finished\nsending output an \u0027OK\u0027 packet is sent.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d425e5584224f75601b832482b76dece82cb9671",
      "old_mode": 33188,
      "old_path": "gdb/remote.c",
      "new_id": "55069559a60a3ab3884dfeadd4bf96ace19cc751",
      "new_mode": 33188,
      "new_path": "gdb/remote.c"
    }
  ]
}