)]}'
{
  "commit": "78e7f66e75f93d49a7accf3a7552b2378533b52b",
  "tree": "614f0f60692a0d8cb938c97c3ab3e6522d7de688",
  "parents": [
    "d0ffdf6482024331dc43d9c221c7afc5863a300b"
  ],
  "author": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Mon Jul 31 11:30:30 2023 -0600"
  },
  "committer": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Thu Aug 10 11:42:38 2023 -0600"
  },
  "message": "Change py-thread-exited.exp to work with gdbserver\n\ngdbserver does not notify gdb of new threads when they are created.\nI\u0027m not sure if this is documented anywhere, but it is mentioned on\nthis page:\n\nhttps://sourceware.org/gdb/wiki/LocalRemoteFeatureParity\n\nSearch for \"Finding new threads in the inferior\".\n\nThis behavior is a bit unfortunate -- I would think that it would be\nbetter to arrange for such notification if something on the gdb side\nis interested.\n\nMeanwhile, this patch fixes py-thread-exited.exp to work around this\nproblem.\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d30677\n\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fd0342bc765e10e089fb9f66401f43f077a64128",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.python/py-thread-exited.c",
      "new_id": "d62133ba59e54d315b219e5370cf94437bfdf2e6",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.python/py-thread-exited.c"
    },
    {
      "type": "modify",
      "old_id": "957585958a2091e0b9b2f37b9d3d79a615dadbbb",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.python/py-thread-exited.exp",
      "new_id": "937816106e2fa7a7d33116599591ecec15de5c2e",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.python/py-thread-exited.exp"
    }
  ]
}