)]}'
{
  "commit": "ab20bdf8efc3e8607e6aa68464901bb109b544db",
  "tree": "dfdb37d887b533520888f38f1440148e73d5fb0e",
  "parents": [
    "613b8ee3f8e2f697445fed3ee2c2748ba0089eea"
  ],
  "author": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Wed May 20 11:22:56 2026 +0100"
  },
  "committer": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Fri Jun 12 14:57:21 2026 +0100"
  },
  "message": "Adjust gdb.python/py-events.exp for Cygwin/MinGW, thread IDs\n\nThis commit fixes a couple issues in gdb.python/py-events.exp for\nCygwin and MinGW:\n\n1) - GDB prints Windows thread IDs in hex:\n\n (gdb) thread\n [Current thread is 1 (Thread 9528.0xa9c)]\n\nThe current code assumes decimal, so we only (incorrectly) extract the\n\"0\" after the dot.\n\n2) - Thread and process ID number spaces are different.\n\nThe current code assumes that the extracted thread ID is the same\nnumber as the extracted process ID, which is not true on Windows.\n\nAlso tested on x86_64-unknown-linux-gnu.\n\nChange-Id: Iebcc07c3ad0845b548334c0d5177b3ab9e9350cf\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "16a290c31c29349344388512b38234dd28b63164",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.python/py-events.exp",
      "new_id": "b07eb2ec9b010f49ae375ee91bdb22804216cfab",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.python/py-events.exp"
    }
  ]
}