)]}'
{
  "commit": "3573490bf0e5d2c550cebed5f4e1a8be0fab2c71",
  "tree": "5666f4036607e082c27afc669edafa9a6613009a",
  "parents": [
    "9e5d27a53096033a5749e2001a0eca48e4b8b472"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Wed Jan 08 16:07:08 2025 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Wed Jan 08 16:07:08 2025 +0100"
  },
  "message": "[gdb/testsuite] Require can_spawn_for_attach in gdb.base/gstack.exp\n\nI ran test-case gdb.base/gstack.exp on a machine with kernel.yama.ptrace_scope\nset to 1 and ran into:\n...\nPASS: gdb.base/gstack.exp: spawn gstack\nptrace: Operation not permitted.^M\nGSTACK-END^M\nPASS: gdb.base/gstack.exp: gstack exits with no error\nPASS: gdb.base/gstack.exp: gstack\u0027s exit status is 0\nFAIL: gdb.base/gstack.exp: got backtrace\n...\n\nFix this by requiring can_spawn_for_attach.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1ad1402e2be3138174ad3475b4f8f2c0f4d73d09",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/gstack.exp",
      "new_id": "f603f2b4ea3e998dc986d73b484bb1d5207ed900",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/gstack.exp"
    }
  ]
}