)]}'
{
  "commit": "a1f2ddd38378c8db63e75daa28b7e304c2fd774f",
  "tree": "75c8b1362699513a6dced987a5838db10b692367",
  "parents": [
    "49a73ab9d345e1cd412a93b34a0b8c166603d80e"
  ],
  "author": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Tue May 17 12:53:32 2022 +0100"
  },
  "committer": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Tue May 17 13:03:07 2022 +0100"
  },
  "message": "Fix gdb.python/py-connection.exp with remote targets\n\nAfter the patch to make gdb_test\u0027s question non-optional when\nspecified, gdb.python/py-connection.exp started failing like so:\n\n  $ make check TESTS\u003d\"gdb.python/py-connection.exp\" RUNTESTFLAGS\u003d\"--target_board\u003dnative-gdbserver\"\n  (gdb) PASS: gdb.python/py-connection.exp: info connections while the connection is still around\n  disconnect^M\n  Ending remote debugging.^M\n  (gdb) FAIL: gdb.python/py-connection.exp: kill the inferior\n\nThe problem is that \"disconnect\" when debugging with the native target\nasks the user whether to kill the program, while with remote targets,\nit doesn\u0027t.\n\nFix it by explicitly killing before disconnecting.\n\nTested with --target_board unix, native-gdbserver, and native-extended-gdbserver.\n\nChange-Id: Icd85015c76deb84b71894715d43853c1087eba0b\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c56aba33e4c40e1463edc246bdbf2306be00c2b9",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.python/py-connection.exp",
      "new_id": "91315eb1af493f3ce5f542dc7e3885369d5156d0",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.python/py-connection.exp"
    }
  ]
}