)]}'
{
  "commit": "706c6624c26b2c954713c872021594bd3a156dd3",
  "tree": "9abd6faefe6e5936a48031e591c541328c8809c0",
  "parents": [
    "05bf17f03b890424312163463754de63cee73074"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Thu Feb 22 11:35:26 2024 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Thu Feb 22 11:35:26 2024 +0100"
  },
  "message": "[gdb/dap] Fix race between dap exit and gdb exit\n\nWhen DAP shuts down due to an EOF event, there\u0027s a race between:\n- gdb\u0027s main thread handling a SIGHUP, and\n- the DAP main thread exiting.\n\nFix this by waiting for DAP\u0027s main thread exit during the gdb_exiting event.\n\nTested on aarch64-linux.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n\nPR dap/31380\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d31380\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "29fe78ecd537d6539b68428f98eb811d79df1ce9",
      "old_mode": 33188,
      "old_path": "gdb/python/lib/gdb/dap/startup.py",
      "new_id": "a2b68996dbaef0f9f0141833b0b726bd14fcc5a8",
      "new_mode": 33188,
      "new_path": "gdb/python/lib/gdb/dap/startup.py"
    },
    {
      "type": "modify",
      "old_id": "a84b1d21e0456c536c291a6b15049f6de8aae884",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.dap/eof.exp",
      "new_id": "05048f2762a600e2e8013f2e220821d3ec52b0b8",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.dap/eof.exp"
    }
  ]
}