)]}'
{
  "commit": "8a841a3579bf1f8eb2414cbc3b2afae6bc59ac8a",
  "tree": "48666126936243929a28942806e946f97994b19f",
  "parents": [
    "6cf20c46e37486b16b565046025c34b2e633dd33"
  ],
  "author": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Tue Feb 22 10:15:07 2022 +0000"
  },
  "committer": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Thu Mar 10 11:35:54 2022 +0000"
  },
  "message": "Re-add zombie leader on exit, gdbserver/linux\n\nSame as the previous patch, but for GDBserver.\n\nIn summary, the current zombie leader detection code in linux-low.cc\nhas a race -- if a multi-threaded inferior exits just before\ncheck_zombie_leaders finds that the leader is now zombie via checking\n/proc/PID/status, check_zombie_leaders deletes the leader, assuming we\nwon\u0027t get an event for that exit (which we won\u0027t in some scenarios,\nbut not in this one), which is a false-positive scenario, where the\nwhole process is simply exiting.  Later when we see the last LWP in\nour list exit, we report that LWP\u0027s exit status as exit code, even\nthough for the (real) parent process, the exit code that counts is the\nchild\u0027s leader thread\u0027s exit code.\n\nLike for GDB, the solution here is to:\n\n   - only report whole-process exit events for the leader.\n   - re-add the leader back to the LWP list when we finally see it\n     exit.\n\nChange-Id: Id2d7bbb51a415534e1294fff1d555b7ecaa87f1d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "442b7d9b81ba1778c74626873f968013dae30bc9",
      "old_mode": 33188,
      "old_path": "gdbserver/linux-low.cc",
      "new_id": "7726a4a0c36c6bafea32fc929b954ed83fd80289",
      "new_mode": 33188,
      "new_path": "gdbserver/linux-low.cc"
    }
  ]
}