)]}'
{
  "commit": "2bbd3cb2289792e8093eec3594b96795df0fc1d4",
  "tree": "368db39c4809bda64f31bf79c44672a98812e487",
  "parents": [
    "f67ddc1be6e447b62c970e372cb6459270a47f53"
  ],
  "author": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Sat May 23 03:08:31 2026 +0100"
  },
  "committer": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Fri Jun 12 14:57:11 2026 +0100"
  },
  "message": "Adjust gdb.base/exitsignal.exp for MinGW, trigger fault\n\ngdb.base/segv.c uses raise(SIGSEGV) to generate a SIGSEGV.  On native\nWindows that does not generate an EXCEPTION_ACCESS_VIOLATION; raise is\na pure userspace construct: it dispatches to the registered SIGSEGV\nhandler if there is one, otherwise calls abort.  GDB therefore never\nsees an exception to intercept.  E.g.:\n\n ...\n continue\n Continuing.\n [Thread 1908.0x3308 (id 2) exited with code 3]\n [Inferior 1 (process 1908) exited with code 03]\n (gdb) FAIL: gdb.base/exitsignal.exp: trigger SIGSEGV (the program exited)\n continue\n The program is not being run.\n ...\n\nReplace the raise with a real null dereference so the kernel actually\nraises an access violation.\n\nNote: I confirmed no other tests use segv.c.  segv.c and normal.c are\nboth \"owned\" by gdb.base/exitsignal.exp.\n\nChange-Id: Ib54d9e6998cf9bfc18dcb5e76d31a9deb0458da4\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a3db6d292db6dda845dc005502ecff2bbea3e474",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/segv.c",
      "new_id": "fd43d95e9b2af708196dc36c7fac6db9d96ddefa",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/segv.c"
    }
  ]
}