)]}'
{
  "commit": "33befefc3d6bf643af9b521e85feaeff0b06ee7b",
  "tree": "9ea8ca9c1f7469ae982ae607f3076da58a2b1cce",
  "parents": [
    "e6dad9621d1f3388dd291af53f8ce264d5107c6b"
  ],
  "author": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Fri Jan 26 18:00:42 2024 +0000"
  },
  "committer": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Fri Apr 26 21:22:47 2024 +0100"
  },
  "message": "Improve vRun error reporting\n\nAfter the previous commit, if starting the inferior process with \"run\"\n(vRun packet) fails, GDBserver reports an error using the \"E.\" textual\nerror packet.  On the GDB side, however, GDB doesn\u0027t yet do anything\nwith the textual error string.  This commit improves that.\n\nThis makes remote debugging output the same as native output, when\npossible, another small step in the \"local/remote parity\" project.\n\nE.g., before, against GNU/Linux GDBserver:\n\n  (gdb) run\n  Starting program: .../gdb.base/run-fail-twice/run-fail-twice.nox\n  Running \".../gdb.base/run-fail-twice/run-fail-twice.nox\" on the remote target failed\n\nAfter, against GNU/Linux GDBserver (same as native):\n\n  (gdb) run\n  Starting program: .../gdb.base/run-fail-twice/run-fail-twice.nox\n  During startup program exited with code 126.\n\nTo know whether we have a textual error message, extend packet_result\nto carry that information.  While at it, convert packet_result to use\nfactory methods, and change its std::string parameter to a plain const\nchar *, as that it always what we have handy to pass to it.\n\nChange-Id: Ib386f267522603f554b52a885b15229c9639e870\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c1a6c137dd4acf85867a0036ec494ad244ce391b",
      "old_mode": 33188,
      "old_path": "gdb/remote.c",
      "new_id": "d425e5584224f75601b832482b76dece82cb9671",
      "new_mode": 33188,
      "new_path": "gdb/remote.c"
    }
  ]
}