)]}'
{
  "commit": "079f190d4cfc6aa9c934b00a9134bc0fcc172d53",
  "tree": "d941f5b1369641f588127308a8f223b9ee6bf39f",
  "parents": [
    "3581f5e4f7c903b53e25c5b8840fa4771ca139aa"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Thu Mar 09 10:45:03 2023 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Thu Mar 09 10:45:03 2023 +0100"
  },
  "message": "[gdb/testsuite] Fix gdb.server/server-kill.exp for remote target\n\nIn commit 80dc83fd0e7 (\"gdb/remote: handle target dying just before a stepi\")\nan observation is made that test-case gdb.server/server-kill.exp claims to\nkill gdbserver, but actually kills the inferior.  Consequently, the commit\nadds testing of killing gdbserver alongside.\n\nThe problem is that:\n- the original observation is incorrect (possibly caused by misreading getppid\n  as getpid)\n- consequently, the test-case doesn\u0027t test killing the inferior, instead it\n  tests killing gdbserver twice\n- the method to get the gdbserver PID added in the commit doesn\u0027t work\n  for target board remote-gdbserver-on-localhost, it returns the\n  PID of the ssh client session instead.\n\nFixing the method for getting the inferior PID gives us fails, and there\u0027s no\nevidence that killing the inferior ever worked.\n\nSo, fix this by reverting the commit and just killing gdbserver, using the\noriginal method of getting the gdbserver PID which does work for target board\nremote-gdbserver-on-localhost.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5622b27f6bf2a7068afda76876723758a600e395",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.server/server-kill.exp",
      "new_id": "0e9df6e1a5f941a5ab6ddb6f0b42f665e625f4aa",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.server/server-kill.exp"
    }
  ]
}