)]}'
{
  "commit": "a47141329c8e984de61ba3c2f2394bcf4328ee92",
  "tree": "7f723e838caa6bbe9f872c5a34dfe98cbb3c4481",
  "parents": [
    "e6a0a281a0bf93bd22247bcd1d68b303dc657845"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Wed Apr 24 15:36:02 2024 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Wed Apr 24 15:36:02 2024 +0200"
  },
  "message": "[gdb/testsuite] Fix gdb.threads/threadcrash.exp for remote host\n\nWith test-case gdb.threads/threadcrash.exp using host board local-remote-host\nand target board remote-gdbserver-on-localhost I run into:\n...\n(gdb) PASS: gdb.threads/threadcrash.exp: test_gcore: continue to crash\ngcore $outputs/gdb.threads/threadcrash/threadcrash.gcore^M\nFailed to open \u0027$outputs/gdb.threads/threadcrash/threadcrash.gcore\u0027 for output.^M\n(gdb) FAIL: gdb.threads/threadcrash.exp: test_gcore: saving gcore\nUNSUPPORTED: gdb.threads/threadcrash.exp: test_gcore: couldn\u0027t generate gcore file\n...\n\nThe problem is that the gcore command tries to save a file on a remote host,\nbut the filename is a location on build.\n\nFix this by using host_standard_output_file.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ffbfd83942c17636bb4420949bfe09758e3ffc4c",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.threads/threadcrash.exp",
      "new_id": "6da70736983254b84080a3055d85f33e82977d24",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.threads/threadcrash.exp"
    }
  ]
}