)]}'
{
  "commit": "203a9824347042e0f7580994cbe7a1eb8dc1e893",
  "tree": "9fed62c560c22c95865c6befcb7be2d8380c28cc",
  "parents": [
    "c11f01dbbdfb8e9f437b13e31ba89c50a6fb8db6"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Sep 27 10:16:57 2021 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Sep 27 10:16:57 2021 +0200"
  },
  "message": "[gdb/testsuite] Test sw watchpoint in gdb.threads/process-dies-while-detaching.exp\n\nThe test-case gdb.threads/process-dies-while-detaching.exp takes about 20s\nwhen using hw watchpoints, but when forcing sw watchpoints (using the patch\nmentioned in PR28375#c0), the test-case takes instead 3m14s.\n\nAlso, it show a FAIL:\n...\n(gdb) continue^M\nContinuing.^M\nCannot find user-level thread for LWP 10324: generic error^M\n(gdb) FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:\ncontinue: watchpoint: continue\n...\nfor which PR28375 was filed.\n\nModify the test-case to:\n- add the hw/sw axis to the watchpoint testing, to ensure that we\n  observe the sw watchpoint behaviour also on can-use-hw-watchpoints\n  architectures.\n- skip the hw breakpoint testing if not supported\n- set the sw watchpoint later to avoid making the test\n  too slow.  This still triggers the same PR, but now takes just 24s.\n\nThis patch adds a KFAIL for PR28375.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ac1aad26ec5776c0e30acc583ca8967c1d9b79e9",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.threads/process-dies-while-detaching.exp",
      "new_id": "ab5a82bef71edf4e0c5c98b4b773d31a9c7b7c7e",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.threads/process-dies-while-detaching.exp"
    }
  ]
}