)]}'
{
  "commit": "7e9d8a3627c8a80b76c250b6881b7eb6fc2f4443",
  "tree": "184f902f541c422d2fc38eed7728558b0e85aae6",
  "parents": [
    "d4a45cd4d1c47244be2e9fe1f82654a4d4968a86"
  ],
  "author": {
    "name": "Alexandra Hájková",
    "email": "ahajkova@redhat.com",
    "time": "Fri Nov 24 14:33:42 2023 +0100"
  },
  "committer": {
    "name": "Alexandra Hájková",
    "email": "ahajkova@redhat.com",
    "time": "Mon Feb 12 15:03:41 2024 +0100"
  },
  "message": "remote.c: Make packet_check_result return a structure\n\npacket_check_result currently returns an packet_result enum.\nIf GDB will recieve an error in a format E.errtext, which\nis possible for some q packets, such errtext is lost if\ntreated by packet_check_result.\nIntroduce a new structure which bundles enum packet_result\nwith possible error message or error code returned by\nthe GDBserver.\nI plan to make more GDBserver response checking functions to use\npacket_check_result to make remote.c code more consistent.\nThis will also allow to use E.errtext more in the future.\n\nBeside adding the unit test, I tested this by modifying\nstore_registers_using_G function to get an error message:\n\n[remote] Sending packet: $GG00000000 ...\n\ngdbserver: Wrong sized register packet (expected 1792 bytes, got 1793)\ngdbserver: Invalid hex digit 71\nKilling process(es): 1104002\n[remote] Packet received: E01\nCould not write registers; remote failure reply \u002701\u0027\n\nReviewed-by: Thiago Jung Bauermann \u003cthiago.bauermann@linaro.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f77548427a4971e19b0bc8f0f282019d9cc20c5a",
      "old_mode": 33188,
      "old_path": "gdb/remote.c",
      "new_id": "14c8b020b1e9b656b1465bac25eddd58af2d1add",
      "new_mode": 33188,
      "new_path": "gdb/remote.c"
    }
  ]
}