)]}'
{
  "commit": "43ca4ec2996a6bfbb8726f1c753aeb85fe0f92a4",
  "tree": "299da693bfdd1c7d761c695a8d2c953e75426b32",
  "parents": [
    "2fb3ca4e88a8266427475596de8c667c9862e953"
  ],
  "author": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Fri Jun 02 23:40:23 2023 +0100"
  },
  "committer": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Mon Apr 29 16:20:46 2024 +0100"
  },
  "message": "gdb/Cygwin: Fix attach pid error message\n\nOn Cygwin, with \"attach PID\":\n\n - GDB first tries to interpret PID as a Windows native PID, and tries\n   to attach to that.\n\n - if the attach fails, GDB then tries to interpret the PID as a\n   Cygwin PID, and attach to that.\n\nIf converting the user-provided PID from a Cygwin PID to a Windows PID\nfails, you get this:\n\n (gdb) attach 12345\n Can\u0027t attach to process 0 (error 2: The system cannot find the file specified.)\n\nNote \"process 0\".\n\nWith the fix in this commit, we\u0027ll now get:\n\n (gdb) attach 12345\n Can\u0027t attach to process 12345 (error 2: The system cannot find the file specified.)\n\nI noticed this while looking at gdb.log after running\ngdb.base/attach.exp on Cygwin.\n\nChange-Id: I05b9dc1f3a634a822ea49bb5c61719f5e62c8514\nApproved-By: Luis Machado \u003cluis.machado@arm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3b3239ab938cb5cee61e5d97e1178a07b19da1cc",
      "old_mode": 33188,
      "old_path": "gdb/windows-nat.c",
      "new_id": "70f955d9797883600376e913e63446fb0d0a3aa7",
      "new_mode": 33188,
      "new_path": "gdb/windows-nat.c"
    }
  ]
}